View ICS1893CFIT_4670516.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

ics1893cf, rev. f, 03/01/07 mar. 2007 idt reserves the right to make changes in the device data identified in this publication without further notice. idt advises its customers to obtain the latest version of all device data to verify that any information being relied upon by the customer is current and accurate. integrated device technology, inc. 3.3-v 10base-t/100base-tx integrated phyceiver ? ics1893cf document type: data sheet document stage: rev. f release features ? supports category 5 cables with attenuation in excess of 24db at 100 mhz. ? single-chip, fully integrated ph y provides pcs, pma, pmd, and autoneg sub layers functions of ieee standard. ? 10base-t and 100base-tx ieee 8802.3 compliant ? single 3.3v power supply ? highly configurable, supports: ? media independent interface (mii) ? auto-negotiation with parallel detection ? node applications, managed or unmanaged ? 10m or 100m full and half-duplex modes ? loopback mode for diagnostic functions ? auto-mdi/mdix cro ssover correction ? low-power cmos (typically 400 mw) ? power-down mode typically 21mw ? clock and crystal supported ? fully integrated, dsp-based pmd includes: ? adaptive equalization and baseline-wander correction ? transmit wave shaping and stream cipher scrambler ? mlt-3 encoder and nrz/nrzi encoder ? small footprint 48-pin 300 mil. ssop package ? also available in small footprint 56-pin 8x8 mlf2 package ? available in industrial temp and lead free general the ics1893cf is a low-power, physical-layer device (phy) that supports the iso/iec 10base-t and 100base-tx carrier-sense multiple access/collision detection (csma/cd) ethernet standards, iso/iec 8802-3. the ics1893cf is intended for mii, node applications that require the auto-mdix feature that automatic ally corrects crossover errors in plant wiring. the ics1893cf incorporates digital-signal processing (dsp) control in its physical-medium dependent (pmd) sub layer. as a result, it can transmit and receive data on unshielded twisted-pair (utp) category 5 cables with attenuation in excess of 24 db at 100mhz. with this ics-patented technology, the ics1893cf can virtually eliminate errors from killer packets. the ics1893cf provides a serial-management interface for exchanging command and status information with a station-management (sta) entity. the ics1893cf media-dependent interface (mdi) can be configured to provide either half- or full-duplex operation at data rates of 10 mb/s or 100mb/s. the ics1893cf is available in a 300-mil 48-lead ssop package. the ics1893cf shares the same proven performance circuitry with the ics1893bf and is a pin-for-pin replacement of the 1893bf. applications: nic cards, pc mot herboards, switches, routers, dsl and cable modems, game machines, printers, network connected appliances , and industrial equipment. clock power leds and phy address twisted- pair interface to magnetics modules and rj45 connector integrated switch mii extended register set interface mux ics1893cf block diagram pcs ? framer ? crs/col detection ? parallel to serial ?4b/5b auto- negotiation 10base-t 100base-t tp_pmd ?mlt-3 ? stream cipher ? adaptive equalizer ? baseline wander correction pma ? clock recovery ? link monitor ? signal detection ? error detection low-jitter clock synthesizer configuration and status 10/100 mii mac interface mii management interface
ics1893cf, rev. f, 03/01/07 mar. 2007 2 revision history ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. revision history ? initial preliminary release of this document, rev a, dated july 10, 2006. ? rev b ? remove all references to ics1893ck; removed package drawing and ordering info. ? rev c ? added ck package and ordering information back to datasheet; removed toc. ? rev e ? changed resistor values in table 9.3 and on figure 9-1, ?ics1893cf 10tcsr and 100tcsr?.
chapter 1 abbreviations and acronyms ics1893cf, rev. f, 03/01/07 mar. 2007 3 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. chapter 1 abbreviations and acronyms table 1-1 lists and interprets the abbreviations and acronyms used throughout this data sheet. table 1-1. abbreviations and acronyms abbreviation / acronym interpretation 4b/5b 4-bit / 5-bit encoding/decoding ansi american national standards institute cmos complimentary metal-oxide semiconductor csma/cd carrier sense multiple access with collision detection cw command override write dsp digital signal processing esd end-of-stream delimiter fddi fiber distributed data interface fll frequency-locked loop flp fast link pulse idl a ?dead? time on the link following a 10 base-t packet, not to be confused with idle iec international electrotechnical commission ieee institute of electrical and electronic engineers iso international standards organization lh latching high ll latching low lmx latching maximum mac media access control max. maximum mbps megabits per second mdi media dependent interface mdix media independent interface crossed mf management frame mii media independent interface min. minimum mlt-3 multi-level transition encoding (3 levels) n/a not applicable nlp normal link pulse no. number nrz not return to zero nrzi not return to ze ro, invert on one
ics1893cf, rev. f, 03/01/07 mar. 2007 4 chapter 1 abbreviations and acronyms ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. osi open systems interconnection oui organizationally unique identifier pcs physical coding sublayer phy physical-layer device the ics1893cf is a physical-lay er device, also referred to as a ?phy? or ?phyceiver?. (the ics1890 is also a physical-layer device.) pll phase-locked loop pma physical medium attachment pmd physical medium dependent ppm parts per million ro read only r/w read/write r/w0 read/write zero sc self-clearing sf special functions sfd start-of-frame delimiter si stream interface, serial in terface, or symbol interface. with reference to the mii/si pin, th e acronym ?si? has multiple meanings. ? generically, si means 'stream interface', and is documented as such in this data sheet. ? however, when the mac inte rface is configured for: ? 10m operations, si is an acronym for 'serial interface'. ? 100m operations, si is an acronym for 'symbol interface'. sqe signal quality error ssd start-of-stream delimiter ssop small shrink outline package sta station management entity stp shielded twisted pair taf technology ability field tp-pmd twisted-pair physical layer medium dependent typ. typical utp unshielded twisted pair table 1-1. abbreviations and acronyms ( continued ) abbreviation / acronym interpretation
chapter 2 conventions and nomenclature ics1893cf, rev. f, 03/01/07 mar. 2007 5 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. chapter 2 conventions and nomenclature table 2-1 lists and explains the conventions and nome nclature used throughout this data sheet. table 2-1. conventions and nomenclature item convention / nomenclature bits ? a bit in a register is identified using t he format ?register.bit?. for example, bit 0.15 is bit 15 of register 0. ? when a colon is used with bits, it indi cates the range of bits. for example, bits 1.15:11 are bits 15, 14, 13, 12, and 11 of register 1. ? for a range of bits, the order is always from the most-significant bit to the least-significant bit. code groups within this table, see the item ?symbols? colon (:) within this table, see these items: ? ?bits? ? ?pin (or signal) names? numbers ? as a default, all numbers use the decimal system (that is, base 10) unless followed by a lowercase letter. a string of numbers followed by a lowercase letter: ? a ?b? represents a binary (base 2) number ? an ?h? represents a hexadecimal (base 16) number ? an ?o? represents an octal (base 8) number ? all numerical references to registers use decimal notation (and not hexadecimal). pin (or signal) names ? all pin or signal names are provided in capital letters. ? a pin name that includes a forward slash ?/? is a multi-function, configuration pin. these pins provide the ability to select between two ics1893cf functions. the name provided: ? before the ?/? indicates the pin name and function when the signal level on the pin is logic zero. ? after the ?/? indicates the pin name and function when the signal level on the pin is logic one. for example, the hw/sw pin selects between hardware (hw) mode and software (sw) mode. when the signa l level on the hw/sw pin is logic: ? zero, the ics1893cf hardware mode is selected. ? one, the ics1893cf software mode is selected. ? an ?n? appended to the end of a pin name or signal name (such as resetn) indicates an active-low operation. ? when a colon is used with pin or signal names, it indicates a range. for example, txd[3:0] repres ents pins/signals txd3, txd2, txd1, and txd0. ? when pin name abbreviations are spelled out, words in parentheses indicate additional description that is not part of the pin name abbreviation. registers ? a bit in a register is identified using t he format ?register.bit?. for example, bit 0.15 is bit 15 of register 0. ? all numerical references to registers use decimal notation (and not hexadecimal). ? when register name abbreviations are spelled out, words in parentheses indicate additional description that is not part of the register name abbreviation.
ics1893cf, rev. f, 03/01/07 mar. 2007 6 chapter 2 conventions and nomenclature ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. signal references ? when referring to signals, the terms: ? ?false?, ?low?, or ?zero? represent signals that are logic zero. ? ?true?, ?high?, or ?one? represent signals that are logic one. ? chapter 9, ?dc and ac operating conditions? defines the electrical specifications for ?logic zero? and ?logic one? signals. symbols ? in this data sheet, code group names are referred to as ?symbols? and they are shown between '/' (slashes). for example, the symbol /j/ represents the first half of the start-of-stream delimiter (ssd1). ? symbol sequences are shown in succession. for example, /i/j/k/ represents an idle followed by the ssd. terms: ?set?, ?active?, ?asserted?, the terms ?set?, ?active?, and ?asserted? are synonymous. they do not necessarily infer logic one. (for example, an active-low signal can be set to logic zero.) terms: ?cleared?, ?de-asserted?, ?inactive? the terms ?cleared?, ?inactive?, and ?de-asserted? are synonymous. they do not necessarily infer logic zero. terms: ?twisted-pair receiver? in reference to the ics1893cf, the term ?twisted-pair receiv er? refers to the set of twisted-pair receive ou tput pins (tp_rxp and tp_rxn). terms: ?twisted-pair transmitter? in reference to the ics1893cf, the term ?twisted-pair trans mitter? refers to the set of twisted-pair transmit output pins (tp_txp and tp_txn). table 2-1. conventions and nomenclature ( continued ) item convention / nomenclature
chapter 3 overview of the ics1893cf ics1893cf, rev. f, 03/01/07 mar. 2007 7 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. chapter 3 overview of the ics1893cf the ics1893cf is a stream processor. during data transmission, it accepts sequential nibbles from its mac (media access control) converts them into a serial bit stream, encodes them, and transmits them over the medium through an external isolation transf ormer. when receiving data, the ics1893cf converts and decodes a serial bit stream (acquired from an is olation transformer that interfaces with the medium) into sequential nibbles. it subsequently pr esents these nibbles to its mac interface. the ics1893cf implements the osi model?s physical laye r, consisting of the following, as defined by the iso/iec 8802-3 standard: ? physical coding sublayer (pcs) ? physical medium attachment sublayer (pma) ? physical medium dependent sublayer (pmd) ? auto-negotiation sublayer the ics1893cf is transparent to the next layer of the osi model, the link laye r. the link layer has two sublayers: the logical link control sublayer and th e mac sublayer. the ics1893cf can interface directly to the mac. the ics1893cf transmits framed packets acquired fr om its mac interface and receives encapsulated packets from another phy, which it translates and presents to its mac interface. note: as per the iso/iec standard, the ics1893cf does not affect, nor is it affected by, the underlying structure of the mac frame it is conveying.
ics1893cf, rev. f, 03/01/07 mar. 2007 8 chapter 3 overview of the ics1893cf ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 3.1 100base-tx operation during 100base-tx data transmission, the ics1893cf accepts packets from a mac and inserts start-of-stream delimiters (ssds) and end-of-stream delimiters (esds) into the data stream. the ics1893cf encapsulates each mac frame, including the preamble, with an ssd and an esd. as per the iso/iec standard, the ics1893cf replaces the first octet of each mac preamble with an ssd and appends an esd to the end of each mac frame. when receiving data from the medium, the ics18 93cf removes each ssd and replaces it with the pre-defined preamble pattern before presenting the nibbles to its mac interface. when the ics1893cf encounters an esd in the received data stream, signifying the end of the frame, it ends the presentation of nibbles to its mac interface. therefore, the local ma c receives an unaltered copy of the transmitted frame sent by the remote mac. during periods when mac frames are being neither transmitted nor received, t he ics1893cf signals and detects the idle condition on the link segment. in the 100base-tx mode, the ics1893cf transmit channel sends a continuous stream of scrambled one s to signify the idle condition. similarly, the ics1893cf receive channel continually monitors its data stream and looks for a pattern of scrambled ones. the results of this signaling and monitoring provide the ics1893cf with the means to establish the integrity of the link segment between itself and its remote link partner and inform its station management entity (sta) of the link status. for 100m data transmission, the ics1893cf mac in terface is configured to provide a 100m media independent interface (mii). 3.2 10base-t operation during 10base-t data transmission, the ics1893cf inse rts only the idl delimiter into the data stream. the ics1893cf appends the idl delimiter to the end of each mac frame. however, since the 10base-t preamble already has a start-of-frame delimiter (sfd), it is not required that the ics1893cf insert an ssd-like delimiter. when receiving data from the medium (such as a twis ted-pair cable), the ics18 93cf uses the preamble to synchronize its receive clock. when the ics1893cf receive clock establishes lock, it presents the preamble nibbles to its mac interface. the 10 m mac interface uses the standard mii interface. in 10m operations, during periods when mac frames are being neither transmitted nor received, the ics1893cf signals and detects normal link pulses. this action allows the integrity of the link segment with the remote link partner to be established and then reported to the ics1893cf?s sta.
chapter 4 operating modes overview ics1893cf, rev. f, 03/01/07 mar. 2007 9 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. chapter 4 operating modes overview the ics1893cf operating modes are typically controlled from software. the ics1893cf register bits are accessible through a standard mii (media independent interface) serial management port. the ics1893cf is configured to support the mac inte rface as a 10m mii or a 100m mii. the protocol on the medium dependent interface (mdi ) can be configured to support either 10m or 100m operations in either half-duplex or full-duplex modes. the ics1893cf is fully compliant wit h the iso/iec 8802-3 standard, as it pertains to both 10base-t and 100base-tx operations. the feature-rich ics1893cf allows easy migration from 10-mbps to 100-mbps operations as well as from systems that require support of both 10m and 100m links. this chapter is an overview of the following ics1893cf modes of operation: ? section 4.1, ?reset operations? ? section 4.2, ?power-down operations? ? section 4.3, ?automatic power-saving operations? ? section 4.4, ?auto-negotiation operations? ? section 4.5, ?100base-tx operations? ? section 4.6, ?10base-t operations? ? section 4.7, ?half-duplex and full-duplex operations? ? section 4.8, ?auto-mdi/mdix crossover?
ics1893cf, rev. f, 03/01/07 mar. 2007 10 chapter 4 operating modes overview ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 4.1 reset operations this section first discusses reset operations in general and then specific ways in which the ics1893cf can be configured for various reset options. 4.1.1 general reset operations the following reset operations apply to all the specif ic ways in which the ics1893cf can be reset, which are discussed in section 4.1.2, ?speci fic reset operations? . 4.1.1.1 entering reset when the ics1893cf enters a reset condition (either through hardware, power-on reset, or software), it does the following: 1. isolates the mac interface input pins 2. drives all mac interface output pins low 3. tri-states the signals on its twisted-pair transmit pins (tp_txp and tp_txn) 4. initializes all its internal modules an d state machines to their default states 5. enters the power-down state 6. initializes all internal latching low (ll), latching high (lh), and latching maximum (lmx) management register bits to their default values 4.1.1.2 exiting reset when the ics1893cf exits a reset condition, it does the following: 1. exits the power-down state 2. latches the serial management port address of the ics1893cf into the extended control register, bits 16.10:6. [see section 7.11.3, ?phy address (bits 16.10:6)? .] 3. enables all its internal modules and state machines 4. sets all management register bits to their default values 5. enables the twisted-pair transmit pins (tp_txp and tp_txn) 6. resynchronizes both its transmit and receive phase-locked loops, which provide its transmit clock (txclk) and receive clock (rxclk) 7. releases all mac interface pins, which takes a maxi mum of 640 ns after the reset condition is removed 4.1.1.3 hot insertion as with the ics189x products, the ics1893cf reset design supports ?hot insertion? of its mii. (that is, the ics1893cf can connect its mac interface to a mac while power is already applied to the mac.)
chapter 4 operating modes overview ics1893cf, rev. f, 03/01/07 mar. 2007 11 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 4.1.2 specific reset operations this section discusses the following specif ic ways that the ics1893cf can be reset: ? hardware reset (usi ng the resetn pin) ? power-on reset (applying power to the ics1893cf) ? software reset (using co ntrol register bit 0.15) note: at the completion of a reset (either hardware, power-on, or software), the ics1893cf sets all registers to their default values. 4.1.2.1 hardware reset entering hardware reset holding the active-low reset n pin low for a minimum of five ref_in clock cycles initiates a hardware reset (that is, the ics1893cf enter s the reset state). during reset, the ics1893cf executes the steps listed in section 4.1.1.1, ?entering reset? . exiting hardware reset after the signal on the resetn pin transitions from a lo w to a high state, the ic s1893cf completes in 640 ns (that is, in 16 ref_in clocks) steps 1 through 5, listed in section 4.1.1.2, ?exiting reset? . after the first five steps are completed, the serial management port is ready for normal operati ons, but this action does not signify the end of the reset cycle. the reset cyc le completes when the transmit clock (txclk) and receive clock (rxclk) are available, which is typically 53 ms after th e resetn pin goes high. [for details on this transition, see section 9.5.16, ?reset: hardware reset and power-down? .] note: 1. the mac interface is not available for use until the txclk and rxclk are valid. 2. the control register bit 0.15 does not represent the st atus of a hardware reset. it is a self-clearing bit that is used to initia te a software reset. 4.1.2.2 power-on reset entering power-on reset when power is applied to the ics1893cf, it waits until the po tential between vdd and vss achieves a minimum voltage before entering reset and executing the steps listed in section 4.1.1.1, ?entering reset? . after entering reset from a power-on condition, the ics1893cf remains in reset for approximately 20 s. (for details on this transition, see section 9.5.15, ?reset: power-on reset? .) exiting power-on reset the ics1893cf automatically exits reset and performs the same steps as for a hardware reset. (see section 4.1.1.2, ?exiting reset? .) note: the only difference between a hardware reset and a power-on reset is that during a power-on reset, the ics1893cf isolates its resetn input pin. all other functionality is the same. as with a hardware reset, control register bit 0.15 does not represent the status of a power-on reset.
ics1893cf, rev. f, 03/01/07 mar. 2007 12 chapter 4 operating modes overview ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 4.1.2.3 software reset entering software reset initiation of a software reset occurs when a managem ent entity writes a logic one to control register bit 0.15. when this write occurs, the ics1893cf ente rs the reset state for two ref_in clock cycles. note: entering a software reset is nearly identical to entering a hardware reset or a power-on reset, except that during a software-initiated reset, the ics1893cf does not enter the power-down state. exiting software reset at the completion of a reset (either hardware, power-on, or software), the ics1893cf sets all registers to their default values. this action autom atically clears (that is, sets equal to logic zero) cont rol register bit 0.15, the software reset bit. therefore, for a software re set (only), bit 0.15 is a self -clearing bit that indicates the completion of the reset process. note: 1. the resetn pin is active low but contro l register bit 0.15 is active high. 2. exiting a software reset is nearly identical to exiting a hardware reset or a power-on reset, except that upon exiting a software-initiated reset, the ics1893 cf does not re-latch its serial management port address into the extended control register. [for in formation on the serial management port address, see section 7.11.3, ?phy address (bits 16.10:6)? .] 3. the control register bit 0.15 does not represent the st atus of a hardware reset. it is a self-clearing bit that is used to initiate a software reset. during a hardware or power-on reset, control register bit 0.15 does not get set to logic one. as a result, this bit 0. 15 cannot be used to indicate the completion of the reset process for hardware or power-on resets. 4.2 power-down operations the ics1893cf enters the power-down state whenever either (1) the resetn pin is low or (2) control register bit 0.11 (the power-down bit) is logic one. in the power-down state, the ics1893cf disables all internal functions and drives all mac interface output pi ns to logic zero except for those that support the mii serial management port. in addition, the ics1893cf tri-states its twisted-pair transmit pins (tp_txp and tp_txn) to achieve an additional reduction in power. there is one significant difference between entering th e power-down state by sett ing control register bit 0.11 as opposed to entering the power-down state during a reset. when the ics1893cf enters the power-down state: ? by setting control register bit 0.11, the ics1893cf ma intains the value of all management register bits except for the latching low (ll), latching high (lh), and latching maximum (lmx) status bits. instead, these ll, lh, and lmx management register bits are re-initialized to their default values. ? during a reset, the ics1893cf sets all of its management register bits to their default values. it does not maintain the state of any management register bit. for more information on power-down operations, see the following: ? section 7.14, ?register 19: extended control register 2? ? section 9.4, ?dc operating characteristics? , which has tables that specify the ics1893cf power consumption while in the power-down state
chapter 4 operating modes overview ics1893cf, rev. f, 03/01/07 mar. 2007 13 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 4.3 automatic powe r-saving operations the ics1893cf has power-saving features that automatic ally minimize its total po wer consumption while it is operating. table 4-1 lists the ics1893cf automatic power-saving features for the various modes. 4.4 auto-negotiation operations the ics1893cf has an auto-negotiation sublayer and provides a control register bit (bit 0.12) to determine whether its auto-negotiation sublayer is enabled or disabled. when enabled, the ics1893cf auto-n egotiation sublayer exchanges tech nology capability data with its remote link partner and automatically selects the hi ghest-performance operating mode it has in common with its remote link partner. for example, if the ics1893cf supports 100base-tx and 10base-t modes ? but its link partner supports 100base-tx and 100base -t4 modes ? the two devices automatically select 100base-tx as the highest-performance common operat ing mode. for details rega rding initialization and control of the auto-negotiation process, see section 6.2, ?functional block: auto-negotiation? . table 4-1. automatic power-saving features, 10base-t and 100base-tx modes power- saving feature mode for ics1893cf 10base-t mode 100base-tx mode disable inter- nal modules in 10base-t mode, the ics1893cf disables all its internal 100base-tx modules. in 100base-tx mode, the ics1893cf disables all its internal 10base-t modules. sta control of automatic power- saving features when an sta sets the state of the ics1893cf extended control register 2, bit 19.0 to logic: ? zero, the 100base-tx modules always remain enabled, even during 10base-t operations. ? one, the ics1893cf automatically disables 100base-tx modules while the ics1893cf is operating in 10base-t mode. when an sta sets the state of the ics1893cf extended control register 2, bit 19.1 to logic: ? zero, the 10base-t modules always remain enabled, even during 100base-tx operations. ? one, the ics1893cf automatically disables 10base-t modules while the ics1893cf is operating in 100base-tx mode.
ics1893cf, rev. f, 03/01/07 mar. 2007 14 chapter 4 operating modes overview ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 4.5 100base-tx operations the ics1893cf 100base-tx mode provides 100base-tx physical layer (phy) services as defined in the iso/iec 8802-3 standard. in the 100base-tx mode, the ics1893cf is a 100m translator between a mac and the physical transmission medium. as such, the ic s1893cf has two interfaces, both of which are fully configurable: one to the mac and one to the link segment. in 100base-tx mode, the ics1893cf provides the following functions: ? data conversion from both parallel-to -serial and serial-to-parallel formats ? data encoding/decoding (4b/5b, nrz/nrzi, and mlt-3) ? data scrambling/descrambling ? data transmission/reception over a twisted-pair medium to accurately transmit and receive data, the ics1 893cf employs dsp-based wave shaping, adaptive equalization, and baseline wander correction. in addi tion, in 100base-tx mode, the ics1893cf provides a variety of control and status means to assist with link segment management. for more information on 100base-tx, see section 6.4, ?functional block: 100base-tx tp-pmd operations? . 4.6 10base-t operations the ics1893cf 10base-t mode provides 10base-t ph ysical layer (phy) services as defined in the iso/iec 8802-3 standard. in the 10base-t mode, the ics1893cf is a 10m transl ator between a mac and the physical transmission medium. in 10base-t mode, the ics1893cf provides the following functions: ? data conversion from both parallel-to -serial and serial-to-parallel formats ? manchester data encoding/decoding ? data transmission/reception over a twisted-pair medium 4.7 half-duplex and ful l-duplex operations the ics1893cf supports half-duplex and full-duplex operations for both 10base-t and 100base-tx applications. full-duplex operatio n allows simultaneous transmission and reception of data, which effectively doubles the link segment throughput to eith er 20 mbps (for 10base-t operations) or 200 mbps (for 100base-tx operations). as per the iso/iec standard, full-duplex operations differ slightly from half-duplex operations. these differences are necessary, as during full-duplex oper ations a phy actively uses both its transmit and receive data paths simultaneously. ? in 10base-t full-duplex operations, the ics1893cf disables its loopback function (that is, it does not automatically loop back data from it s transmitter to its receiver) and disables its sqe test function. ? in both 10base-t and 100base-tx full-duplex operati ons, the ics1893cf asserts its crs signal only in response to receiv e activity while its col signal always remains inactive. for more information on half-duplex and full-duplex operations, see the following sections: ? section 7.2, ?register 0: control register? ? section 7.2.8, ?duplex mode (bit 0.8)? ? section 7.3, ?register 1: status register? ? section 7.6, ?register 4: auto-negotiation register?
chapter 4 operating modes overview ics1893cf, rev. f, 03/01/07 mar. 2007 15 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 4.8 auto-mdi/mdix crossover (new) the ics1893cf includes the auto-mdi/mdix crossover feat ure. in a typical cat 5 ethernet installation the transmit twisted pair signal pins of the rj45 connector are crossed over in the cat 5 wiring to the partners receive twisted pair signal pins and receive twisted pair to the partners transmit twisted pair. this is usually accomplished in the wiring plant. hubs generally wi re the rj45 connector crossed to accomplish the crossover. two types of cat 5 cables (straight and crossed) are available to achieve the correct connection. the auto-mdi/mdix featur e automatically corrects for miss-wir ed installations by automatically swapping transmit and receive signal pairs at the ph y when no link results. au to-mdi/mdix is automatic, but may be disabled for test purposes using the amdix_en pin or by writing mdio register 19 bits 9:8 in the mdio register. the auto-mdi/m dix function is independent of auto-negotiation and preceeds auto-negotiation when enabled.
ics1893cf, rev. f, 03/01/07 mar. 2007 16 chapter 5 interface overviews ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. chapter 5 interface overviews the ics1893cf mac interface is fully configurable, thereby allowing it to accommodate many different applications. this chapter includes overviews of the following mac-to-phy interfaces: ? section 5.1, ?mii data interface? ? section 5.2, ?serial management interface? ? section 5.3, ?twisted-pair interface? ? section 5.4, ?clock reference interface? ? section 5.5, ?status interface?
chapter 5 interface overviews ics1893cf, rev. f, 03/01/07 mar. 2007 17 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 5.1 mii data interface the ics1893cf?s mac interface is the media independent interface (mii) operating at either 10 mbps or 100 mbps. the ics1893cf mac interface is configured fo r the mii data interface mode, data is transferred between the phy and the mac as framed, 4-bit parallel nibbles. in addition, the interface also provides status and control signals to synchronize the transfers. the ics1893cf provides a full complement of the iso/iec-specified mii signa ls. its mii has both a transmit and a receive data path to synchronously exchange 4 bits of data (that is, nibbles). ? the ics1893cf?s mii transmit data path includes the following: ? a data nibble, txd[3:0] ? a transmit data clock to synchronize transfers, txclk ? a transmit enable signal, txen ? the txer pin is not available on the ics1893cf ? the ics1893cf?s mii receive data path includes the following: ? a separate data nibble, rxd[3:0] ? a receive data clock to synchronize transfers, rxclk ? a receive data valid signal, rxdv both the mii transmit clock and the mii receive clock are pr ovided to the mac/reconciliation sublayer by the ics1893cf (that is, the ics1893cf source s the txclk and rxclk signals to the mac). clause 22 also defines as part of t he mii a carrier sense signal (crs) a nd a collision detect signal (col). the ics1893cf is fully compliant with these definition s and sources both of these signals to the mac. when operating in: ? half-duplex mode, the ics1893cf asserts the carr ier sense signal when data is being either transmitted or received. while opera ting in half-duplex mode, the ic s1893cf also asserts its collision detect signal to indicate that data is being received while a transm ission is in progress. ? full-duplex mode, the ics1893cf asserts the carrier sense signal only when receiving data and forces the collision detect signa l to remain inactive. as mentioned in section 4.1.1.3, ?hot insertion? , the ics1893cf design allows hot insertion of its mii. that is, it is possible to connect its mii to a mac when power is already applied to the mac. to support this functionality, the ics1893cf isolates its mii signals an d tri-states the signals on all twisted-pair transmit pins (tp_txp and tp_txn) during a power-on reset. upon completion of the reset process, the ics1893cf enables its mii and enables its twisted-pair transmit signals.
ics1893cf, rev. f, 03/01/07 mar. 2007 18 chapter 5 interface overviews ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 5.2 serial management interface the ics1893cf provides an iso/iec compliant, two-wir e serial management interface as part of its mac interface. this serial management interface is used to exchange control, status, and configuration information between a station management entity (sta) and the physical layer device (phy), that is, the ics1893cf. the iso/iec standard also specifies a frame structure and protocol for this interface as well as a set of management registers that provide the sta with access to a ph y such as the ics1893cf. a serial management interface is comprised of two signals: a bi-directional data pin (mdio) along with an associated input pin for a clock (mdc). the clock is used to synchronize all data transfers between the ics1893cf and the sta. in addition to the iso/iec defined registers, the ic s1893cf provides several ex tended status and control registers to provide more refined control of the mii and mdi interfaces. for example, the quickpoll detailed status register provides the ability to acquire the most-impor tant status functions with a single mdio read. note: in the ics1893cf, the mdio and mdc pins remain active for all the mac interface modes (that is, 10m mii, 100m mii, 100m symbol, and 10m serial). 5.3 twisted-pair interface for the twisted-pair interface, the ics1893cf uses 1:1 ratio transformers for both transmit and receive. better operation results from using a split ground plane through the transformer. in this case: ? the rj-45 transformer windings must be on the chassis ground plane along with the bob smith termination. ? the ics1893cf system ground plane must include the ics1893cf-side transformer windings along with the 49.9 ? resistors and the 100 nf capacitor. ? the transformer provides the isolation with one set of windings on one ground plane and another set of windings on the second ground plane. 5.3.1 twisted-pair transmitter the twisted-pair transmitter driver uses an h-brid ge configuration. idt transformer requirements: ? turns ratio 1:1 ? chokes may be used on chip or cable side or both sides ? no power connections to the transformer. tr ansformer power is supplied by the ics1893cf ? midcom 7090-37 or equivalent symetrical magnetics are used figure 5-1 shows the design for the ics1893cf twisted-pair interface. ? two 49.9 ? 1% resistors are in series with a 100 nf capacitor to ground between them. these components form a network that connects across both pairs of twisted pairs a and b. ? both twisted pairs a and b have an assigned plus and minus. note: 1. keep all tx traces as short as possible. 2. when longer board twisted pair traces are used, 50 ? -characteristic board trace impedance is desirable.
chapter 5 interface overviews ics1893cf, rev. f, 03/01/07 mar. 2007 19 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. figure 5-1. ics1893cf twisted pair * * for backward compatibility, refer to the the ?1893c alternate schemati c? application note. 49.9 ? 1% to rj-45 1:1 system ground plane chassis ground plane 75 ? separate ground plane ideally, for these traces z o = 50 ? . nc tp_ap 12 tp_an 13 49.9 ? 1% 49.9 ? 1% to rj-45 75 ? 0.1 f ideally, for these traces z o = 50 ? . center tap tp_bp 16 tp_bn 15 ics1893cf chassis gnd 49.9 ? 1% 100 nf center tap 100 nf nc
ics1893cf, rev. f, 03/01/07 mar. 2007 20 chapter 5 interface overviews ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 5.4 clock reference interface the ref_in pin provides the ics1893cf clock refere nce interface. the ics1893cf requires a single clock reference with a freque ncy of 25 mhz 50 parts per million. th is accuracy is necessary to meet the interface requirem ents of the iso/ieee 8802-3 st andard, specifically clauses 22.2.2.1 and 24.2.3.4. the ics1893cf supports two clock source configurations: a cmos oscillator or a cmos driver. the input to ref_in is cmos (10% to 90% vdd), not ttl. altern ately, a 25mhz crystal may be used. the oscillator specifications are shown in table 5.2. figure 5-2. crystal or oscillator operation 33 pf ref_in 47 ref_out 46 25.000mhz 33 pf 10 pf ref_in 47 ref_out 46 cmos 25.000 mhz 33 ohm nc crystal oscillator ics1893cf ics1893cf
chapter 5 interface overviews ics1893cf, rev. f, 03/01/07 mar. 2007 21 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. if a crystal is used as the clocking source, connect it to both the ref_in (pin 47) and ref_out (pin 46) pins of the ics1893cf. a pair of bypass capacitors on eith er side of the crystal are connected to ground. the crystal is used in the parallel resonance or anti-resonance mode. the value of the load caps serve to adjust the final frequency of the crystal oscillation. typica l applications would use 33pf load caps. the exact value will be affected by the board routing capacitance on ref_in and re f_out pins. smaller load capacitors raise the frequency of oscillation. on ce the exact value of load capaci tance is established it will be the same for all boards using the same specification cryst al. the best way to measure the crystal frequency is to measure the frequency of txclk (pin 37) using a frequency counter with a 1 second gate time. using the buffered output txclk prevents the crystal frequency from being affected by the measurement. the crystal specification is shown in table 5.1. table 5-1. 25mhz crystal specification specifications symbol mini mum typical maximum unit fundamental frequency (tolerance is sum of freq., temp., stability and aging.) f0 24.99875 25.00000 25.00125 mhz freq. tolerance ? f/f 50 ppm input capacitance cin 3 pf table 5-2. 25mhz oscillator specification specifications symbol mini mum typical maximum unit output frequency f0 24.99875 25.00000 25.00125 mhz freq. stability (including aging) ? f/f 50 ppm duty cycle cmos level one-half vdd tw/t 35 65 % vih 2.79 volts vil 0.33 volts period jitter tjitter 500 ps input capacitance cin 3 pf
ics1893cf, rev. f, 03/01/07 mar. 2007 22 chapter 5 interface overviews ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 5.5 status interface the ics1893cf provides five multi-function configurat ion pins that report the results of continual link monitoring by providing signals that are intended fo r driving leds. (for the pin numbers, see table 8.6.) note: 1. during either a power-on reset or a hardware rese t, each multi-function configuration pin is an input that is sampled when the ics1893cf exits the reset state. after sampling is complete, these pins are output pins that ca n drive status leds. 2. a software reset does not affect the state of a multi- function configuration pin. during a software reset, all multi-function configuration pins are outputs. 3. each multi-function configuration pin must be pulled either up or down with a resistor to establish the address of the ics1893cf. leds may be placed in series with these resistors to provide a designated status indicator as described in table 5-3. use 1k ? resistors. caution: all pins listed in table 5-3 must not float. 4. as outputs, the asserted state of a multi-function configuration pin is the inverse of the sense sampled during reset. this inversion provides a signal that can illuminate an led during an asserted state. for example, if a multi-function configuration pin is pulled down to ground through an led and a current-limiting resistor, then the sampled sense of the input is low. to illuminate th is led for the asserted state, the output is driven high. 5. adding 10k ? resistors across the leds ensures the ph y address is fully defined during slow vdd power-ramp conditions. 6. phy address 00 tri-states the mii interface. (do not select phy address 00 unless you want the mii tri-stated.) table 5-3. pins for monitoring the data link pin led driven by the pin?s output signal p0ac ac (link ac tivity) led p1cl cl ( c o l lisions) led p2li li ( l ink i ntegrity) led p3td td ( t ransmit d ata) led p4rd rd ( r eceive d ata) led
chapter 5 interface overviews ics1893cf, rev. f, 03/01/07 mar. 2007 23 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. figure 5-3 shows typical biasing and led connections for the ics1893cf. figure 5-3. ics1893cf led - phy interface ics1893cf 10k ? 86 4 3 1 p4rd p3td p2li p1cl p0ac rec trans link activity 10k ? led 1k ? 10k ? led 1k ? 10k ? vdd col led 1k ? 10k ? this circuit decodes to phy address = 1. notes: 1. all led pins must be set during reset. 2. caution: phy address 00 tri-states the mii interface. don?t use phy address 00. 3. for more reliable address capture during power-on reset, add a 10k ? resistor across the led.
ics1893cf, rev. f, 03/01/07 mar. 2007 24 chapter 6 functional blocks ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. chapter 6 functional blocks this chapter discusses the following ics1893cf functional blocks. ? section 6.1, ?functional block: media independent interface? ? section 6.2, ?functional block: auto-negotiation? ? section 6.3, ?functional block: 100base-x pcs and pma sublayers? ? section 6.4, ?functional block: 100base-tx tp-pmd operations? ? section 6.5, ?functional block: 10base-t operations? ? section 6.6, ?functional block: management interface?
chapter 6 functional blocks ics1893cf, rev. f, 03/01/07 mar. 2007 25 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 6.1 functional block: me dia independent interface all ics1893cf mii interface signals are fully compliant with the iso/iec 8802-3 standard. in addition, the ics1893cf miis can support two data transfer rates: 25 mhz (for 100base-tx operations) and 2.5 mhz (for 10base-t operations). the media independent interface (mii) consists of two primary components: 1. an interface between a mac (media access contro l sublayer) and the phy (that is, the ics1893cf). this mac-phy part of the mii c onsists of three subcomponents: a. a synchronous transmit interface that incl udes the following signals: (1) a data nibble, txd[3:0] (2) a delimiter, txen (3) a clock, txclk b. a synchronous receive interface t hat includes the followings signals: (1) a data nibble, rxd[3:0] (2) an error indicator, rxer (3) a delimiter, rxdv (4) a clock, rxclk c. a media status or control interface that consis ts of a carrier sense signal (crs) and a collision detection signal (col). 2. an interface between the phy (the ics1893cf) and an sta (station management entity). the sta-phy part of the mii is a two-wire, serial ma nagement interface that consists of the following: a. a clock (mdc) b. a synchronous, bi-directional data signal (mdio) that provides an sta with access to the ics1893cf management register set the ics1893cf management register set (discussed in chapter 7, ?management register set? ) consists of the following: ? basic management registers. as defined in the iso/iec 8802-3 standard, these registers include the following: ? control register (register 0), whic h handles basic device configuration ? status register (register 1), which repo rts basic device capabilities and status ? extended management registers. as defined in the iso/iec 8802-3 standard, the ic s1893cf supports extended registers that provide access to the organizationally unique iden tifier and all auto-negotiation functionality. ? ics (vendor-specific) management registers. the ics1893cf provides vendor-specific registers for enhanced phy operations. among these is the quickpoll detailed status register that provides a comprehensive and consolidated set of real-time phy information. reading the quickpoll re gister enables the mac to obtain comprehensive status data with a single register access.
ics1893cf, rev. f, 03/01/07 mar. 2007 26 chapter 6 functional blocks ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 6.2 functional block: auto-negotiation the auto-negotiation logic of the ics1893cf has the following main functions: ? to determine the capabilitie s of the remote link part ner, (that is, the device at the other end of the link segment?s medium or cable) ? to advertise the capabilit ies of the ics1893cf to the remote link partner ? to establish a protocol with the remote link partne r using the highest-perfor mance operating mode that they have in common the design of the ics1893cf auto-negotiation sublay er supports both legacy 10base-t connections as well as new connections that have multiple technolo gy options for the link. for example, when the ics1893cf has the auto-nego tiation process enabled and it is o perating with a 10base-t remote link partner, the ics1893cf monitors the link and automatically selects the 10base-t operating mode ? even though the remote link partner does not support auto-ne gotiation. this process, ca lled parallel detection, is automatic and transparent to the re mote link partner and allows the ics1893cf to function seamlessly with existing legacy network structures without any management intervention. (for an overview of the auto-negotiation process, see section 4.4, ?auto-negotiation operations? .) 6.2.1 auto-negotiation general process the auto-negotiation sublayer uses a physical signalin g technique that is transparent at the packet level and all higher protocol levels. this technique build s on the link pulse mechanism employed in 10base-t operations and is fully compliant with clause 28 of the iso/iec 8802-3 standard. during the auto-negotiation process, both the ics1893cf and its remote link partner use fast link pulses (flps) to simultaneously ?advertise? (that is, exch ange) information on their respective technology capabilities as follows: 1. for the auto-negotiation process to take place, both the ics1893cf and its remote link partner must first both support and be enabled for auto-negotiation. 2. the ics1893cf obtains the data for its flp bursts from the auto-negotiation advertisement register (register 4). 3. both the ics1893cf and the remote link partner substitute fast link pulse (flp) bursts in place of the normal link pulses (nlps). in each flp burst, t he ics1893cf transmits information on its technology capability through its link cont rol word, which includes link c onfiguration and status data. 4. similarly, the ics1893cf places th e auto-negotiation data received from its remote link partner's flp bursts into the auto-negot iation link partner abilit y register (register 5). 5. after the ics1893cf and its remote link partner exchange technology capa bility information, the ics1893cf auto-negotiation sublayer contrasts t he data in registers 4 and 5 and automatically selects for the operating mode the highest-priority technology that both register 4 and 5 have in common. (that is, both the ics1893cf and its remote link partner use a predetermined priority list for selecting the operating mode, thereby ensuring that bo th sides of the link make the same selection.) as follows from annex 28b of the iso/ iec 8802-3 standard, the pre-determined technology priorities are listed from 1 (highest priority) to 5 (lowest priority): (1) 100base-tx full duplex (2) 100base-t4. (the ics1893cf does not support this technology.) (3) 100base-tx (half duplex) (4) 10base-t full duplex (5) 10base-t (half duplex)
chapter 6 functional blocks ics1893cf, rev. f, 03/01/07 mar. 2007 27 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 6. to indicate that the auto-negotiat ion process is complete, the ics1893cf sets bits 1.5 and 17.4 high to logic one. after successful completion of the auto-negotiation process, the ics1893cf auto-negotiation sublayer performs the following steps: a. it sets to logic one the status register?s auto-n egotiation complete bit (b it 1.5, which is also available in the quickpoll register as bit 17.4). b. it enables the negotiated link technology (such as the 100base transmit modules and 100base receive modules). c. it disables the unused technologies to reduce the overall power consumption. 6.2.2 auto-negotiation: parallel detection the ics1893cf supports parallel detection. it is theref ore compatible with networks that do not support the auto-negotiation process. when enabled, the auto-negotiation sublayer can detect legacy 10base-t link partners as well as 100base-tx link partners that do not have an auto-negotiation capability. the auto-negotiation sublayer performs this parallel det ection function when it does not get a response to its flp bursts. in these situations, the auto-ne gotiation sublayer performs the following steps: 1. it sets the lp_autoneg_able bit (bit 6.0) to logic zero, thereby identifying the remote link partner as not being capable of executing th e auto-negotiation process. 2. it sets the bit in the auto-negot iation link partner abilit ies register that corres ponds to the 'parallel detected' technology [for example, half-duplex, 10b ase-t (bit 5.5) or half-duplex, 100base-tx (bit 5.7)]. 3. it sets the status register?s auto-negotiation comple te bit (bit 1.5) to logic one, indicating completion of the auto-negoti ation process. 4. it enables the detected link technology and disables the unused technologies. a remote link partner that does not support the auto-negotiation process does not respond to the transmitted flp bursts. the ics1893cf detects this situation and responds according to the data it receives. the ics1893cf can receive one of five potential responses to the flp bursts it is transmitting: flp bursts, 10base-t link pulses (that is, normal link pulses), scrambled 100base idles, nothing, or a combination of signal types. a 10base-t link partner transmits only normal link pulses when idle. when the ics1893cf receives normal link pulses, it concludes that the remote link partner is a device that can use only 10base-t technology. a 100base-tx node without an auto-negot iation sublayer transmits 100m scrambled idle symbols in response to the flp bursts. upon receip t of the scrambled idles, the ics1893cf concludes that its remote link partner is a 100base-tx node that does not support the auto -negotiation process. for both 10base-t and 100base-tx nodes without an auto-n egotiation sublayer, the ic s1893cf clears bit 6.0 to logic zero, indicating that the link partner cannot perform the auto-negotiation process. if the remote link partner responds to the flp bursts with flp bursts, then the link partner is a 100base-tx node that can support the auto-negotiation process. in this case, the ics1893cf sets to logic one the auto-negotiation expansion register?s link pa rtner auto-negotiation ability bit (bit 6.0). if the auto-negotiation sublayer do es not receive any signal when moni toring the receive channel, then the quickpoll detailed status register?s sig nal detect bit (bit 17.3) is set to lo gic one, indicating that no signal is present. another possibility is that the ics1893c f senses that it is receiving multip le technology indications. in this situation, the ics1893cf cannot determine which technol ogy to enable. it informs the sta of this problem by setting to logic one the auto-negotiation expansi on register?s parallel detection fault bit (bit 6.4).
ics1893cf, rev. f, 03/01/07 mar. 2007 28 chapter 6 functional blocks ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 6.2.3 auto-negotiation: remote fault signaling if the remote link partner detects a f ault, the ics1893cf reports the remotely detected fault to the sta by setting to logic one the remote fault detected bit(s), 1. 4, 5.13, 17.1, and 19.13. in general, the reception of a remote fault means that the remote link partner ha s a problem with the integrity of its receive channel. similarly, if the ics1893cf detects a link fault, it trans mits a remote fault-detected condition to its remote link partner. in this situ ation, the ics1893cf sets to logic one the au to-negotiation li nk partner ability register?s remote fault indication bit (bit 4.13). for details, see section 7.14.3, ?remot e fault (bit 19.13)? and section 7.3.9, ?remote fault (bit 1.4)? . 6.2.4 auto-negotiation: reset and restart if enabled, execution of the ics1893cf auto-n egotiation process occurs at power-up and upon management request. there are two primary ways to begin the auto-negotiation state machine: ? ics1893cf reset ? auto-negotiation restart 6.2.4.1 auto-negotiation reset during a reset, the ics1893cf initializes its auto-neg otiation sublayer modules to their default states. (that is, the auto-negotiation arbitration state machine and the auto-negotiation progress monitor reset to their idle states.) in addition, the auto-negotiation progress monitor status bits are all set to logic zero. this action occurs for any type of reset (hardware reset, software reset, or power-on reset). 6.2.4.2 auto-negotiation restart as with a reset, during an auto-negotiation restar t, the ics1893cf initializes the auto-negotiation arbitration state machine and the auto-negotiation pr ogress monitor modules to their default states. however, during an auto-negotiation restart, the auto -negotiation progress monitor status bits maintain their current state. only three events can alter the state of the auto-negotiation progress monitor status bits after a restart: (1) an sta read operation, (2) a reset, or (3) the auto-ne gotiation arbitration state machine progressing to a higher state or value. the auto-negotiation progress monitor status bits c hange only if they are progressing to a state with a value greater than their current state (that is, a state with a higher logical value than that of their current state). for a detailed explanation of these bits and their operation, see section 6.2.5, ?auto-negotiation: progress monitor? . after the auto-negotiation arbitrat ion state machine reaches its final state (which is auto-negotiation complete), only an sta read of the quickpoll detailed status register or an ics1893cf reset can alter these status bits. any of the following situations initiates a restart of the ics1893cf auto-negotiation sublayer: ? a link failure ? in software mode: ? writing a logic one to the control register?s restar t auto-negotiation bit (bit 0.9), which is a self- clearing bit. ? toggling the control register?s auto-negotiation enable bit (bit 0.12) from a logic one to a logic zero, and back to a logic one.
chapter 6 functional blocks ics1893cf, rev. f, 03/01/07 mar. 2007 29 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 6.2.5 auto-negotiation: progress monitor under typical circumstance s, the auto-negotiation sublayer can establish a connection with the ics1893cf?s remote link partner. ho wever, some situations can preven t the auto-negotiation process from properly achieving this goal. for these situations , the ics1893cf has an auto-negotiation progress monitor to provide detailed status information to its station management (sta) entity. with this status information, the sta can diagnose the failure mechanism and ? in some situations ? establish the link by correcting the problem. when enabled, the auto-negotiation process typically requ ires less than 500 ms to execute, independent of the link partner's ability to perfor m the auto-nego tiation process. typically , an sta polls both the auto-negotiation complete bit (bit 1.5) and the link status bit (bit 1.2) to determine when a link is successfully established, either through auto-negotiati on or parallel detection. the sta can then poll the auto-negotiation link part ner ability register and det ermine the highest-perfo rmance operati ng mode in common with the capabilitie s it is advertising. 6.3 functional block: 100b ase-x pcs and pma sublayers the ics1893cf is fully compliant with clause 24 of the iso/iec s pecification, which defines the 100base-x physical coding sublayer (pcs) and physical medium attach ment (pma) sublayers. 6.3.1 pcs sublayer the ics1893cf 100base-x pcs sublayer provides two interfaces: one to a mac and the other to the ics1893cf pma sublayer. an ics1893?s pcs sublayer performs the transmit, receive, and control functions and consists of the following: ? pcs transmit sublayer, which provides the following: ? parallel-to-serial conversion ? 4b/5b encoding ? collision detection ? pcs receive sublayer, which provides the following: ? serial-to-parallel conversion ? 4b/5b encoding ? carrier detection ? code group framing ? pcs control functions, which provide: ? assertion of the crs (carrier sense) signal ? assertion of the col (collision detection) signal 6.3.2 pma sublayer the ics1893cf 100base-x pma sublayer consists of tw o interfaces: one to the physical coding sublayer and the other to the physical medium dependent sublay er. functionally, the pma sublayer is responsible for the following: ? link monitoring ? carrier detection ? nrzi encoding/decoding ? transmit clock synthesis ? receive clock recovery
ics1893cf, rev. f, 03/01/07 mar. 2007 30 chapter 6 functional blocks ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 6.3.3 pcs/pma transmit modules both the pcs and pma sublayers have transmit modules. 6.3.3.1 pcs transmit module the ics1893cf pcs transmit module accepts nibbles from the mac interface and converts the nibbles into 5-bit ?code groups? (referred to here as ?symbols ?). in addition, the pcs tr ansmit module performs a parallel-to-serial conversion on the symbols, and subseque ntly passes the resulting serial bit stream to the pma sublayer. the first 16 nibbles of each mac frame represent the frame preamble. the pcs replaces the first two nibbles of the frame preamble with the start-of-stream delimiter (ssd), that is, the symbols /j/k/. after receipt of the last frame nibble, detected when tx_e n = false, the pcs appends to the end of the frame an end-of-stream delimiter (esd), that is, the sym bols /t/r/. (the ics1893cf pcs does not alter any other data included within the frame.) the pcs transmit module also perfor ms collision detection. in complianc e with the iso/iec specification, when the transmission and reception of data occur simultaneously and the ics1893cf is in: ? half-duplex mode, the ics1893cf asserts the collision detection signal (col). ? full-duplex mode, col is always false. 6.3.3.2 pma transmit module the ics1893cf pma transmit module accepts a serial bit stream from its pcs and converts the data into nrzi format. subsequently, the pma passes the nrzi bit stream to the twisted-pair physical medium dependent (tp-pmd) sublayer. the ics1893cf pma transmit module uses a digital pll to synthesize a transmit clock from the clock reference interface. 6.3.4 pcs/pma receive modules both the pcs and pma sublayers have receive modules. 6.3.4.1 pcs receive module the ics1893cf pcs receive module accepts both a serial bit stream and a clock signal from the pma sublayer. the pcs receive module converts the bit stream from a serial format to a parallel format and then processes the data to detect the presence of a carrier. when a link is in the idle state, the pcs receive module receives idle symbols. (all bits are logic one.) upon receiving two non-contiguous zeros in the bit stream, the pcs receive module examines the ensuing bits and attempts to locate the start-of-s tream delimiter (ssd), that is, the /j/k/ symbols. upon verification of a valid ssd, the pcs receive modu le substitutes the first two standard nibbles of a frame preamble for the detected ssd. in addition , the pcs receive module uses the ssd to begin framing the ensuing data into 5-bit code symbols. the final pcs receive module performs 4b/5b decoding on the symbols and then synchronously passes the resulting nibbles to the mac interface. the receive state machine continues to accept pma data, convert it from serial to parallel format, frame it, decode it, and pass it to the mac interface. during th is time, the receive state machine alternates between receive and data states. it continues this process until detecting one of the following: ? an end-of-stream delimiter (esd, that is, the /t/r/ symbols) ? an error ? a premature end (idles)
chapter 6 functional blocks ics1893cf, rev. f, 03/01/07 mar. 2007 31 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. upon receipt of an esd, the receive state machine re turns to the idle state without passing the esd to the mac interface. detection of an er ror forces the receive state machine to assert the receive error signal (rx_er) and wait for the next symbol. if the ics1893cf receive state machine detects a premature end, it forces the assertion of the rx_er signal, sets the premature end bit (bit 17.5) to logic one, and transitions to the idle state. 6.3.4.2 pma receive modules the ics1893cf has a pma receive module that provides the following functions: ? nrzi decoding the receive module performs the nrzi decoding on the serial bit stream received from the twisted-pair physical medium dependent (tp-pmd) sublayer. it conver ts the bit stream to a unipolar, positive, binary format that the pma subsequently passes to the pcs. ? receive clock recovery the receive clock recovery function consists of a ph ase-locked loop (pll) that operates on the serial data stream received from the pmd sublayer. this pll automatically synchroni zes itself to the clock encoded in the serial data stream and then provides both a recovered clock and data stream to the pcs. ? link monitoring ? the ics1893cf?s pma link monitoring function observes the receive clo ck pll. if the receive clock pll cannot acquire ?lock? on the serial data stre am, it asserts an error signal. the status of this error signal can be read in the quickpoll detailed st atus register?s pll lock error bit (bit 17.9). this bit is a latching high (lh) bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) ? in addition, the ics1893cf?s pma link monitor functi on continually audits the state of the connection with the remote link partner. it asserts a receive channe l error if a receive signal is not detected or if a pll lock error occurs. these errors, in turn, generate a link fault and force the link monitor function to clear both the status register?s link st atus bit (bit 1.2) and the quickpoll detailed status register?s link status bit (bit 17.0). 6.3.5 pcs control signal generation for the pcs sublayer, there are two control signals: a carrier sense signal (crs) and a collision detect signal (col). the crs control signals is generated as follows: 1. when a logic zero is detected in an idle bit st ream, the receive functions examines the ensuing bits. 2. when the receive functions find the first two non-contiguous zero bits, the receive state machine moves into the carrier detect state. 3. as a result, the boolean receiv ing variable is set to true. 4. consequently, the carrier sense state machine moves into the carrier sense ?o n? state, which asserts the crs signal. 5. if the pcs functions: a. cannot confirm either the /i/j/ (idle, j) symbo ls or the /j/k/ symbols, the receive error signal (rx_er) is asserted, and the receive state machine returns to the idle state. in idle, the boolean receiving variable is set to false, thereby causing the carrier sense state machine to set the crs signal to false. b. can confirm the /i/j/k/ symbols, then the receiv e state machine transitions to the ?receive? state. the col control signal is generated by the transmit modules. for details, see section 6.3.3.1, ?pcs transmit module? .
ics1893cf, rev. f, 03/01/07 mar. 2007 32 chapter 6 functional blocks ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 6.3.6 4b/5b encoding/decoding the 4b/5b encoding methodology maps each 4-bit nibble to a 5-bit symbol (also called a ?code group?). there are 32 five-bit symbols, which include the following: ? of the 32 five-bit symbols, 16 five-bit symb ols are required to represent the 4-bit nibbles. ? the remaining 16 five-bit symbol s are available for control functi ons. the ieee standard defines 6 symbols for control, and the remaining 10 symbols of this grouping are invalid. the 6 control symbols include the following: ? /h/, which represents a halt, also used to signify a transmit error ? /i/, which represents an idle ? /j/, which represents the first symbol of the start-of-stream delimiter (ssd) ? /k/, which represents the second symbol of the start-of-stream delimiter (ssd) ? /t/, which represents the first symbol of the end-of-stream delimiter (esd) ? /r/, which represents the second symbol of the end-of-stream delimiter (esd) if the ics1893cf pcs receives: ? one of the 10 undefined symbols, it sets its quickp oll detailed status register?s invalid symbol bit (bit 17.7) to logic one. ? a halt symbol, it sets the halt sy mbol detected bit in its quickpoll detailed status register (bit 17.6) to logic one. note: an sta can force the ics1893cf to transmit symbols that are typi cally classified as invalid, by both (1) setting the extended control register?s transmit invalid codes bit (bit 16.2) to logic one and (2) asserting the associated txer signal. for more information, see section 7.11.7, ?invalid error code test (bit 16.2)? . 6.4 functional block: 100b ase-tx tp-pmd operations the ics1893cf supports both 10base-t and 100base-tx operations. for 100base-tx operations, the tp-pmd module performs stream-cipher scrambling/descrambling and mlt-3 encoding/decoding (3-level, multi-level transition) in compliance with the ansi standard x3.263: 199x fddi tp-pmd as defined in the specification for 100base-tx twis ted-pair physical media dependent (tp-pmd) sublayer. the ics1893cf?s tp-pmd also performs dc restoration (that is, baseline wander correction) and adaptive equalization on the received signals. note: 1. for an overview of 100base-tx operations, see section 4.5, ?100base-tx operations? . 2. for more information on the twisted-pair in terface, see section 5.3, ?twisted-pair interface? . 6.4.1 100base-tx operation: stream cipher scrambler/descrambler when the ics1893cf is operating in 100base-tx mode, it employs a stream cipher scrambler/descrambler that complies with the ansi st andard x3.263: 199x fddi tp-pmd. the purpose of the stream cipher scrambler is to spread the transmission spectrum to minimize electromagnetic compatibility problems. the st ream cipher descrambler restores the received serial bit stream to its unscrambled form. the ics1893cf ?seeds? (that is, initializes) the trans mit stream cipher shift register by using the ics1893cf phy address from table 7-16 , which minimizes crosstalk and noise in repeater applications. the mac interface bypasses the stream cipher scrambler /descrambler when in the 100m symbol interface mode.
chapter 6 functional blocks ics1893cf, rev. f, 03/01/07 mar. 2007 33 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 6.4.2 100base-tx operation: mlt-3 encoder/decoder when operating in the 100base-tx mode, the ics1 893cf tp-pmd sublayer employs an mlt-3 encoder and decoder. during data transmission, the tp-pmd encoder converts the nrzi bit stream received from the pma sublayer to a 3-level multi-level transition code. the three levels are -1, 0, and +1. the results of mlt-3 encoding provide a reduction in the transmitted energy over the critical frequency range from 20 mhz to 100 mhz. the tp-pmd mlt-3 decoder converts the received three-level signal back to an nrzi bit stream. 6.4.3 100base-tx operation: dc restoration the ics1893cf?s 100base-tx operations uses a stream -cipher scrambler to minimize peak amplitudes in the frequency spectrum. however, the nature of the stream cipher and mlt-3 encoding is such that long sequences of consecutive zeros or ones can exis t. these unbalanced data patterns produce an undesirable dc component in the data stream known as ?baseline wander?. baseline wander adversely affects the noise immunity of the receiver, because the ?baseline? signal moves or ?wanders? from its nominal dc value. the ics 1893cf uses a unique technique to restore the dc component ?lost? by the medium. as a result, the design is very robust, immune to noise and independent of the data stream. 6.4.4 100base-tx operation: adaptive equalizer the ics1893cf has a tp-pmd sublayer that uses adap tive equalization circuitry to compensate for signal amplitude and phase distortion incurred from the transmission medium. at a data rate of 100 mbps, the transmission medium (that is, the cabl e) introduces significant signal di stortion because of high-frequency attenuation and phase shift. the high-frequency loss o ccurs primarily because of the cable skin effect that causes the conductor resistance to rise as the square of the frequency rises. the ics1893cf has an adaptive equalizer that accu rately compensates for th ese losses in shielded twisted-pair (stp) and un shielded twisted-pair (utp) cables. t he dsp-based adaptive equalizer uses a technique that compensates for a wide range of cable lengths. the optimizing parameter for the equalization process is the overall bit error rate of the ics1893cf. this technique closes the loop on the entire data reception pr ocess and provides a very high overall reliability. 6.4.5 100base-tx operation: twisted-pair transmitter the ics1893cf uses the same twisted-pair transmi t pins (tp_txp and tp_txn) for both 10base-t and 100base-tx operations. each twisted-pair transmitter m odule is a current-driven, differential driver that can supply either of the following: ? a two-level 10base-t (that is, manchester-encoded) signal ? a three-level 100base-tx (that is, mlt-3 encoded) signal the ics1893cf interfaces with the medium through an is olation transformer (sometimes referred to as a magnetic module). the ics1893cf?s transmitter uses wave-shaping techniques to control the output signal rise and fall times (thereby eliminating the need fo r external filters) and in terfaces directly to the isolation transformer. note: 1. in reference to the ics1893cf, the term ?twisted-pai r transmitter? re fers to the set of twisted-pair transmit output pins (tp_txp and tp_txn). 2. for information on the 10base-t twisted-pair transmitter, see section 6.5.11, ?10base-t operation: twisted-pair transmitter? .
ics1893cf, rev. f, 03/01/07 mar. 2007 34 chapter 6 functional blocks ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 6.4.6 100base-tx operation: twisted-pair receiver the ics1893cf uses the same twisted-pair receive pins (tp_rxp and tp_rxn) for both 10base-t and 100base-tx operations. the internal twisted-pair receiver modules interface with the medium through an isolation transformer. the 100base-tx receiver module accepts and processes a differential three-level 100base-tx (that is, mlt-3 encoded) signal from th e isolation transformer. (i n contrast, the 10base-t receiver module accepts and processes a differential two-level, manchester- encoded, 10base-t signal from the isolation transformer). note: 1. in reference to the ics1893cf, the term ?twisted-p air receiver? refers to the set of twisted-pair receive output pins (tp_rxp and tp_rxn). 2. for information on the 10base -t twisted-pair receiver, see section 6.5.12, ?10base-t operation: twisted-pair receiver? . 6.4.7 100base-tx operation: isolation transformer the ics1893cf interfaces with a medium through isol ation transformers. the phy requires two isolation transformers: one for its twisted-pair transmitter and the other for its twisted-pair receiver. these isolation transformers provide both physical isolatio n as well as the means for coupling a signal between the ics1893cf and the medium for both 10base-t and 100base-tx operations. note: for information on isolation transformers (also referred to as magnetic modules), see section 5.3, ?twisted-pair interface? . 6.5 functional block: 10base-t operations when configured for 10base-t mode, the ics1893cf mac interface is configured to provide 10m mii (media independent interface). the twisted-pair interface is automatically configured to provide a two-level, manchester-encoded signal at the voltage levels specified in the iso/iec standard. (for more information on the twiste d-pair interface, see section 5.3, ?twisted-pair interface? .) the 10base-t and 100base-tx operations differ as follows. 10base-t operations are fundamentally simpler than 100base-tx operations. the data rate is slower, requiring less encoding than 100base-tx operations. in addition, the bandwidth requirements (a nd therefore the line attenua tion issues) are not as severe as with 100-mhz operations. consequently, wh en an ics1893cf is set for 10base-t operations, it requires fewer internal circuits in contrast to 10 0base-tx operations. (for an overview of 10base-t operations, see section 4.6, ?10base-t operations? .). 6.5.1 10base-t operation: manchester encoder/decoder during data transmission the ics1893cf acquires data from its mac interface in 4-bit nibbles. the ics1893cf converts this data into a manchester-encoded signal for presentation to its mdi, as required by the iso/iec specification. in a manchester-encoded signal, all logic: ? ones are: ? positive during the first half of the bit period ? negative during the second half of the bit period ? zeros are: ? negative during the first half of the bit period ? positive during the second half of the bit period
chapter 6 functional blocks ics1893cf, rev. f, 03/01/07 mar. 2007 35 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. during 10base-t data reception, a manchester decoder translates the serial bit stream obtained from the twisted-pair receiver (mdi) into an nrz bit stream. the manchester decoder then passes the data to the mac interface in parallel format. manchester-encoded signals have the following advantages: ? every bit period has an encoded clock. ? the split-phase nature of the signal always provides a zero dc level regardless of the data (that is, there is no baseline wander phenomenon). the primary disadvantage in using manchester-encoded si gnals is that it doubles the data rate, making it operationally prohibitive for 100-mhz operations. 6.5.2 10base-t operation: clock synthesis the ics1893cf synthesizes the clocks required for synchronizing data transmission. in 10base-t mode, the mac interface provides a 10m mii (media independent interface): ? 10m mii interface, the ics1893cf synthesizes a 2.5-mhz clock for nibble-wide transactions 6.5.3 10base-t operation: clock recovery the ics1893cf recovers its receive clock from th e manchester-encoded data stream obtained from its twisted-pair receiver using a phas e-locked loop (pll). the ics1893cf t hen uses this recovered clock for synchronizing data transmission bet ween itself and the mac. receive- clock pll acquisi tions begin with reception of the mac frame preamble and continue as long as the ics1893cf is receiving data. 6.5.4 10base-t operation: idle an ics1893cf transmits normal link pulses on its mdi in the absence of data. during this time the link is idle, and the ics1893cf periodically transmits link pulses at a rate of one link pulse every 16 ms in compliance with the iso/ie c 8802-3 standard. in 10base-t mode, t he ics1893cf continues transmitting link pulses even while receivi ng data. this situation doe s not generate a collision de tect signal (col) because link pulses indicate an idle state for a link. 6.5.5 10base-t operation: link monitor when an ics1893cf is in 10base-t mode, its link monitor function observes the data received by the 10base-t twisted-pair receiver to determine the link status. the results of this continual monitoring are stored in the link status bit. the station management entity (sta) can access the link status bit in either the status register (bit 1.2) or the quickpoll detailed status register (bit 17.0). when the link status bit is: ? zero, either a valid link is not estab lished or the link is momentarily dropp ed since either the last read of the link status bit or the last reset of the ics1893cf. ? one, a valid link is established. the ics1893cf link status bit is a latching low (ll) bi t. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) the criteria used by the link monitor function to declare a link either valid or invalid depends upon these factors: the present state of the lin k, whether its smart squelch function is enabled, and the incoming data.
ics1893cf, rev. f, 03/01/07 mar. 2007 36 chapter 6 functional blocks ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. when the 10base-t link is: ? invalid, and the smart squelch function is: ? disabled (bit 18.0 is logic one), the link monito r function must detect at least one of the following events before transitioning its link from the invalid state to the valid state: ? more than seven, iso/iec-defined, normal link pulses (nlps) ? any valid data ? enabled (bit 18.0 is logic zero), the link monito r function must detect at least one of the following events before transitioning its link from the invalid state to the valid state: ? more than seven, iso/iec-defined, normal link pulses (nlps) ? any valid data followed by a valid idl ? valid, and the smart squelch function is: ? disabled (bit 18.0 is logic one), the link monitor func tion continues to report its link as valid as long as it continues to detect any of the following: ? iso/iec-defined, normal link pulses (nlps) ? any valid data ? enabled (bit 18.0 is logic zero), the link monitor function continues to report its link as valid as long as it continues to detect any of the following: ? iso/iec-defined, normal link pulses (nlps) ? any valid data followed by a valid idl ? valid, the link monitor function declares the link as inva lid if it receives neithe r data nor nlps (that is, the link shows either no activity or inconsistent activity ) for more than 81 to 83 ms. in this case the link monitor function sets the link status bit to logic zero. note: 1. an ics1893cf receives ?valid data? when its twiste d-pair receiver phase-locked loop can acquire lock and extract the receive clock from the incoming da ta stream for a minimum of three consecutive bit times. 2. when a link is invalid and the link monitor function detects the presence of data, the ics1893cf does not transition the link to the valid state until after the reception of the present packet is complete. 3. enabling or disabling the smart squelch fu nction affects the link monitor function. 4. a transition from the invalid state to the valid state does not automatically update the latching-low link status bit. 6.5.6 10base-t operation: smart squelch the smart squelch function imposes more stringent re quirements on the link monitor function regarding the definition of a valid link, thereby providing a level of insurance that spurious noise is not mistaken for a valid link during cable installation. an sta can control the execution of the ics1893cf smart squelch function using bit 18.0 (the smart squelch inhibit bit in the 10base-t operat ions register). when bit 18.0 is logic: ? zero (the default), an ics1893cf enables its smart squelch function. in this case, the link monitor must confirm the presence of both data and a valid id l at the end of the packet before declaring a link valid. ? one, an ics1893cf disables or inhibits its smart sq uelch function. in this case, the link monitor does not have to confirm the presence of an idl to declar e a link valid (that is, the reception of any data is sufficient). in 10base-t mode, an ics1893cf appends an idl to the end of each packet during data transmission. the receiving phy (the remote link partner) sees this idl and removes it from the data stream.
chapter 6 functional blocks ics1893cf, rev. f, 03/01/07 mar. 2007 37 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 6.5.7 10base-t operation: carrier detection the ics1893cf has a 10base-t carrier detection function that establishes the state of its carrier sense signal (crs), based upon the state of its transmit and receive state machines. these functions indicate whether the ics1893cf is (1) transmitti ng data, (2) receiving data, or (3 ) in a collision state (that is, the ics1893cf is both transmitting and receiving data on its twisted-pair medium, as defined in the iso/iec 8802-3 standard). when the ics1893cf is configured for: ? half-duplex operations, the ics1893cf asserts its crs signal when either transmitting or receiving data. ? full-duplex operations, the ics1893cf asserts it s crs signal only when it is receiving data. 6.5.8 10base-t operation: collision detection the ics1893cf has a 10base-t collision detection func tion that establishes the state of its collision detection signal (col) based upon both (1) the state of its receiver state machine and (2) the state of its transmit state machine. when the ics1893cf is operating in: ? half-duplex mode, the ics1893cf asserts its col si gnal to indicate it is receiving data while transmission of data is also in progress. ? full-duplex mode, the ics1893cf always sets its col signal to false. 6.5.9 10base-t operation: jabber the ics1893cf has an iso/iec compliant jabber dete ction function that, when enabled, monitors the data stream sent to its twisted-pa ir transmitter to ensure that it does not exceed the 10base-t jabber activation time limit (that is, the maximum tr ansmission time). for more information, see section 9.5.18, ?10base-t: jabber timing? . when the jabber detection function detects that its transmission time exceeds the maximum jabber activation time limit and jabber detection is enabled, the ics18 93cf asserts its collision detect (col) signal. during this iso/iec specifi ed ?jabber de-activation time?, the ic s1893cf transmit data stream is interrupted and prevented from reaching its twisted-pa ir transmitter. during this time, when interrupting the data stream and asserting its col signal, the ic s1893cf transmits normal link pulses and sets its quickpoll detailed status register?s ja bber detected bit (bit 17.2) to logic one. this bit is a latching high (lh) bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) the ics1893cf provides an sta with the ability to disable the jabber de tection function us ing the jabber inhibit bit (bit 18.5 in the 10 base-t operations register). setting bit 18.5 to logic: ? zero (the default) enables th e jabber detection function. ? one disables the jabb er detection function. 6.5.10 10base-t operation: sqe test the ics1893cf has an iso/iec compliant signal qua lity error (sqe) test function used exclusively for 10base-t operations. when enabled, the ics1893cf performs the sqe test at the completion of each transmitted packet (that is, whenever its tx_en signal transitions from asserted to de-asserted). when the ics1893cf executes its sqe test, it asserts the col signal to its mac interface for a pre-determined time duration (iso/iec specified). [for more information, see section 9.5.17, ?10base-t: heartbeat timing (sqe)? .]
ics1893cf, rev. f, 03/01/07 mar. 2007 38 chapter 6 functional blocks ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. an ics1893cf sqe test function is: ? enabled only when all the fo llowing conditio ns are true: ? the ics1893cf is in node mode. ? the ics1893cf is in half-duplex mode. ? the ics1893cf has a valid link. ? the 10base-t operations register?s sqe test inhi bit bit (bit 18.2) is logic zero (the default). ? the ics1893cf tx_en signal has transitioned from asserted (high) to de-asserted (low). ? disabled whenever any of the following are true: ? the ics1893cf is in full-duplex mode. ? the ics1893cf detects a link failure. ? the ics1893cf sqe test inhibit bit (bit 18.2) in t he 10base-t operations register is logic one. [this bit provides the station manageme nt entity (sta) with the ability to disable the sqe test function.] note: 1. in 10base-t mode, a bit time has a typical duration of 100 ns. 2. the sqe test also has the name 10base-t heartbeat. for details on the sqe waveforms, see section 9.5.17, ?10base-t: heartbeat timing (sqe)? . 6.5.11 10base-t operation: twisted-pair transmitter the 10base-t twisted-pair transmitte r is functionally similar to the 10 0base-tx twisted-pair transmitter. the primary differences are in the data rate and signa ling, as specified in the iso/iec specifications. for more information, see section 6.4.5, ?100base-tx operation: twisted-pair transmitter? . 6.5.12 10base-t operation: twisted-pair receiver the 10base-t twisted-pair receiver is functionally similar the 100base-tx twisted-pair receiver. the primary differences are in the data rate and signaling, as specified in the iso/ie c specifications. for more information, see section 6.4.6, ?100base-tx oper ation: twisted-pair receiver? . 6.5.13 10base-t operation: auto polarity correction the ics1893cf can sense and then automatically correc t a signal polarity that is reversed on its twisted-pair receiver inputs. a signa l polarity reversal occurs when the input signals on an ics1893cf?s tp_rxp and tp_rxn pins are crossed or swapped (a problem that can occur during network installation or wiring). the ics1893cf accomplishes reversed signal polarity detection and correction by examining the signal polarity of the normal link pulses (nlps). in 10ba se-t mode, an ics1893cf transmits and receives nlps when its link is in the idle state. in 100base-tx mode, an ics1893cf transmits and receives nlps during auto-negotiation. an sta can control this feature us ing the 10base-t operations register bit 18.3, the auto polarity-inhibit bit. when this bit is logic: ? zero, the ics1893cf automatically senses and corrects a revers ed or inverted signal polarity on its twisted-pair receive pins (tp_rxp and tp_rxn). ? one, the ics1893cf disables this feature.
chapter 6 functional blocks ics1893cf, rev. f, 03/01/07 mar. 2007 39 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. when an ics1893cf detects a reversed signal polarity on its twisted-pair receiver pins and the auto polarity-inhibit bit is also logic zero (enabled), th e ics1893cf (1) automatically corrects the data stream and (2) sets its polarity reversed bit (bit 18.14) to logi c one, to indicate to the sta that this situation exists. bit 18.14 is a latching high (lh) bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) note: the ics1893cf will not complete the auto-mdix function for an inverted polarity cable. this is a rare event with modern manufactured cables. full auto-negotiation and auto polarity correction will complete when the auto-mdix fu nction is disabled. software control for the auto-mdix function is available in mdio register 19 bits 9:8. 6.5.14 10base-t operation: isolation transformer the 10base-t isolation transformer operates the same as the 100base-tx isolation transformer. in fact, in a typical ics1893cf application they are the same unit. for more information, see section 6.4.7, ?100base-tx operation: isolation transformer? . 6.6 functional block: management interface as part of the mac interface, the ics1893cf prov ides a two-wire serial management interface which complies with the iso/iec 8802-3 standard mii serial management interface. this interface is used to exchange control, status, and configuration informati on between a station management entity (sta) and the physical layer device (phy). the phy and sta exchange this data through a pre-defined set of management registers. the iso/iec standard spec ifies the following components of this serial management interface: ? a set of registers ( section 6.6.1, ?management register set summary? ) ? the frame structure ( section 6.6.2, ?management frame structure? ) ? the protocol in compliance with the iso/iec specification, the ic s1893cf implementation of the serial management interface provides a bi-directional data pin (mdi o) along with a clock (mdc ) for synchronizing the exchange of data. these pins remain active in al l ics1893cf mac interface mo des (that is, the 10/100 mii, 100m symbol, and 10m serial interface modes). 6.6.1 management register set summary the ics1893cf implements a management register set that adheres to the iso/iec standard. this register set (discussed in detail in chapter 7, ?management register set? ) includes the mandatory ?basic? control and status registers and the iso/iec ?extended? registers as well as some ics-specific registers. 6.6.2 management frame structure the serial management interface is a synchronous, bi-directional, two-wire, serial interface for the exchange of configuration, control, and status data between a phy, such as an ics1893cf, and an sta. all data transferred on an mdio signal is synchronized by its m dc signal. the phy and sta exchange data through a pre-defined register set. the ics1893cf complies with the iso/iec defined management frame structure and protocol. this structure supports both read and write operations. table 6-1 summarizes the management frame structure.
ics1893cf, rev. f, 03/01/07 mar. 2007 40 chapter 6 functional blocks ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. note: the management frame structure starts from and returns to an idle condition. however, the idle periods are not part of the management frame structure. 6.6.2.1 management frame preamble the ics1893cf continually monitors its serial manageme nt interface for either valid data or a management frame (mf) preamble, based upon the setting of the mf preamble suppression bit, 1.6. when the mf preamble suppression is disabled, an ics1893cf waits for a mf preamble which indicates the start of an sta transaction. a management frame preamble is a pa ttern of 32 contiguous logic one bits on the mdio pin, along with 32 corresponding clock cycles on the mdc pin. the ics1893cf supports the ma nagement frame (mf) preamble suppression capability on its management interface, thereby providing a method to shorten the management frame and provide an sta with faster access to the management registers. the ability to process manag ement frames that do not have a preamble is prov ided by the management frame preamble suppression bit, (bit 1.6 in the ics1893c f?s status register). this is an iso/iec defined status bit that is intended to provide an indication of whether or not a phy supports the mf preamble suppression feature. in order to ma intain backward compatibility with the ics1890, which did not support mf preamble suppression, the ics1893cf mf preamb le suppression bit is a command override write bit which defaults to a logic zero. an sta can enable mf preamble suppression by writing a logic one to bit 1.6 subsequent to a write of logic one to the comm and override bit, 16.15. for an explanation of the command override write bits, see section 7.1.2, ?management register bit access? . 6.6.2.2 management frame start a valid management frame includes a start-of-frame delimiter, sfd, immediatel y following the preamble. the sfd bit pattern is 01b and is synchr onous with two clock cycles on the mdc pin. 6.6.2.3 management frame operation code a valid management frame includes an operation code (op) immediately following the start-of-frame delimiter. there are two valid operation codes: one fo r reading from a management register, 10b, and one for writing to a management register, 01b. the ics1 893cf does not respond to the codes 00b and 11b, which the iso/iec specification defines as invalid. 6.6.2.4 management frame phy address the two-wire, serial management interface is specified to allow busing (that is, the sharing of the two wires among multiple phys). the management frame includes a 5-bit phy address field, phyad, allowing for 32 unique addresses. an sta unique ly identifies each of the phys that share a single serial management interface by using this 5-bit phy address field, phyad. table 6-1. management frame structure summary frame field data comment acronym frame function pre preamble (bit 1.6) 11..11 32 ones sfd start of frame 01 2 bits op operation code 10/01 (read/write) 2 bits phyad phy address (bits 16.10:6) aaaaa 5 bits regad register address rrrrr 5 bits ta turnaround z0/10 (read/write) 2 bits data data ddd..dd 16 bits
chapter 6 functional blocks ics1893cf, rev. f, 03/01/07 mar. 2007 41 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. upon receiving a valid sta transaction, during a power-on or hardware reset an ics1893cf compares the phyad field included within the management frame with th e value of its phyad bits stored in register 16. (for information on the phyad bits, see table 7-16 .) an ics1893cf responds to all transactions that match its stored address bits. 6.6.2.5 management frame register address a management frame includes a 5-bit register address fi eld, regad. this field i dentifies which of the 32 management registers are involved in a transaction between an sta and a phy. 6.6.2.6 management frame operational code a management frame includes a 2-bit operational code field, op. if the operation code is a: ? read, the regad field identifies the register used as the source of data returned to the sta by the ics1893cf. ? write, the regad identifies the dest ination register that is to receive the data sent by the sta to the ics1893cf. 6.6.2.7 management frame turnaround a valid management frame includes a turn-around field (ta), which is a 2-bit time space between the regad field and the data field. this time allows an ics1893cf and an sta to avoid contentions during read transactions. during an operation that is a: ? read, an ics1893cf remains in the high-impedance state during the first bit time and subsequently drives its mdio pin to logic zero for the second bit time. ? write, an ics1893cf waits while the sta transmits a logic one, followed by a logic zero on its mdio pin. 6.6.2.8 management frame data a valid management frame includes a 16-bit data field for exchanging the register contents between the ics1893cf and the sta. all management registers are 16 bits wide, matching the width of the data field. during a transaction that is a: ? read, (op is 10b) the ics1893cf obtains the contents of the register identified in the regad field and returns this data to the sta sy nchronously with its mdc signal. ? write, (op is 01b) the ics1893cf stores the value of the data field in the register identified in the regad field. if the sta attempts to: ? read from a non-existent ics1893cf register, the ic s1893cf returns logic one for all bits in the data field, ffffh. ? write to a non-existent ics1893cf register, the ics1893cf isolates the data field of the management frame from every reaching the registers. note: the first data bit transmitted and received is the most-significant bit of a management register, bit x.15. 6.6.2.9 serial management interface idle state the mdio signal is in an idle state during the time between sta transactions. when the serial management interface is in the idle state, the ics1893c f disables (that is, tri-states) its mdio pin, which enters a high-impedance state. the iso/iec 8802-3 standard requires that an mdio signal be idle for at least one bit time between management transacti ons. however, the ics1893cf does not have this limitation and can support a continual bit stream on its mdio signals.
ics1893cf, rev. f, 03/01/07 mar. 2007 42 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. chapter 7 management register set the tables in this chapter detail the functionality of the bits in the management register set. the tables include the register locations, the bit positions, th e bit definitions, the sta read/write access types, the default bit values, and any special bi t functions or capabilitie s (such as self-cleari ng). following each table is a description of each bit. this ch apter includes the following sections: ? section 7.1, ?introduction to management register set? ? section 7.2, ?register 0: control register? ? section 7.3, ?register 1: status register? ? section 7.4, ?register 2: phy identifier register? ? section 7.5, ?register 3: phy identifier register? ? section 7.6, ?register 4: auto-negotiation register? ? section 7.7, ?regis ter 5: auto-negotiation link partner ability register? ? section 7.8, ?register 6: auto-negotiation expansion register? ? section 7.9, ?register 7: auto-negotiation next page transmit register? ? section 7.10, ?register 8: au to-negotiation next page li nk partner ability register? ? section 7.11, ?register 16: extended control register? ? section 7.12, ?register 17: quic k poll detailed status register? ? section 7.13, ?register 18: 10base-t operations register? ? section 7.14, ?register 19: extended control register 2?
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 43 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.1 introduction to mana gement register set this section explains in general terms the manageme nt register set discussed in this chapter. (for a summary of the management register set, see section 6.6.1, ?management register set summary? .) 7.1.1 management register set outline this section outlines the ics1893 cf management register set. table 7-1 lists the iso/iec-specified management register set that the ics1893cf implements. table 7-2 lists the idt-specific registers that the ic s1893cf implements. these registers enhance the performance of the ics1893cf and provide the stat ion management entity (sta) with additional control and status capabilities. table 7-1. iso/iec-specified management register set register address register name basic / extended 0 control basic 1status basic 2,3 phy identifier extended 4 auto-negotiation advertisement extended 5 auto-negotiation link partner ability extended 6 auto-negotiation expansion extended 7 auto-negotiation next page transmit extended 8 auto-negotiation ne xt page link partner ability extended 9 through 15 reserved by ieee extended 16 through 31 vendor-specifi c (idt) registers extended table 7-2. idt-specific registers register address register name basic / extended 16 extended control extended 17 quickpoll detailed status extended 18 10base-t operations extended 19 extended control 2 extended 20 through 31 reserved by idt extended
ics1893cf, rev. f, 03/01/07 mar. 2007 44 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.1.2 management register bit access the ics1893cf management registers include on e or more of the following types of bits: 7.1.3 management register bit default values the tables in this chapter specify fo r each register bit the default value, if one exists. the ics1893cf sets all management register bits to their default values after a reset. table 7-4 lists the valid default values for ics1893cf management register bits. note: the ics1893cf has a number of reserved bits th roughout the management registers. most of these bits provide enhanced test modes. the management register tables provide the default values for these bits. the sta must not change th e value of these bits under any circumstance. if the sta inadvertently changes the default values of these reserved register bits, normal operation of the ics1893cf can be affected. table 7-3. description of management register bit types management register bit types bit symbol description read-only ro an sta can obtain the value of a ro register bit. however, it cannot alter the value of (that is, it cannot write to) an ro register bit. the ics1893cf isolates any sta attempt to write a value to an ro bit. command override write cw an sta can read a value from a cw register bit. however, write operations are conditional, based on the value of the command register override bit (bit 16.15). when bit 16.15 is logic: ? zero (the default), the ics1893cf isolates sta attempts to write to the cw bits (that is, cw bits cannot be altered when bit 16.15 is logic zero). ? one, the ics1893cf permits an sta to alter the value of the cw bits in the subsequent register writ e. (bit 16.15 is self-clearing and automatically clears to zero on the subsequent write.) read/write r/w an sta can unconditionally read from or write to a r/w register bit. read/write zero r/w0 an sta can unconditionally read from a r/w0 register bit, but only a ?0? value can be written to this bit. table 7-4. range of possible valid default values for ics1893cf register bits default condition default value ? indicates there is no default value for the bit 0 indicates the bit?s default value is logic zero 1 indicates the bit?s default value is logic one state of pin at reset for some bits, the default value depends on the state (that is, the logic value) of a particular pin at reset (that is, the logic value of a pin is latched at reset). an example of pins that have a default condit ion that depends on th e state of the pin at reset are the phy / led pins (p0ac, p1cl, p2li, p3td, and p4rd) discussed in the following sections: ? section 5.5, ?status interface? ? section 7.11, ?register 16: extended control register? ? section 8.2.2, ?multi-fun ction (multiplexed) pins: phy address and led pins?
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 45 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.1.4 management register bit special functions this section discusses the types of special functions for the management register bits. 7.1.4.1 latching high bits the purpose of a latching high (lh) bit is to record an event. an lh bit records an event by monitoring an active-high signal and then latching this active-high sig nal when it triggers (that is, when the event occurs). a latching high bit, once set to logic one, remains set un til either a reset occurs or it is read by an sta. immediately following an sta read of an lh bit, the ics1 893cf latches the current state of the signal into the lh bit. when an sta reads an lh bit: ? once, the ll bit provides the sta with a history of wh ether or not the event has ever occurred. that is, this first read provides the sta with a history of the condition and latches the current state of the signal into the ll bit for the next read. ? twice in succession, the lh bit provides the sta with the current state of the monitored signal. 7.1.4.2 latching low bits as with latching high bits, the purpose of a latching low (l l) bit is also to record an event. an ll bit records an event by monitoring an active-low signal and then latching this active-l ow signal when it triggers (that is, when the event occurs). a latching low bit, once cleared to logic zero, remains clea red until either a reset occurs or it is read by an sta. immediately following an sta read of an ll bit, the ics1893cf latches the current state of the active-low signal into the ll bit. when an sta reads an ll bit: ? once, the ll bit provides the sta with a history of wh ether or not the event has ever occurred. that is, this first read provides the sta with a history of the condition and latches the current state of the signal into the ll bit for the next read. ? twice in succession, the ll bit provides the st a with the current state of the monitored signal. 7.1.4.3 latching maximum bits for the ics1893cf, the purpose of latching maximum (lmx ) bits is to track the progress of internal state machines. the lmx bits act in combination with other lmx bits to save the maximum collective value of a defined group of lmx bits, from the most-significant bit to the least-significant bit. for example, assume a group of lmx bits is defined as r egister bits 13 through 11. if these bits first have a value of 3o (octal) and then the state machine they are monitoring advances to state: ? 2o, then the 2o value does not get latched. ? 4o (or any other value greater than 3o), then in this case, the value of 4o does get latched. lmx bits retain their value until either a reset occurs or they are read by an sta. immediately following an sta read of a defined group of lmx bits, the ics1893cf latches the current state of the monitored state machine into the lmx bits. when an sta reads a group of lmx bits: ? once, the lmx bits provide the sta with a history of the maximum value that the state machine has achieved and latches the current state of the stat e machine into the lmx bits for the next read. ? twice in succession, the lmx bits provide the sta wit h the current state of the monitored state machine. 7.1.4.4 self-clearing bits self-clearing (sc) bits automatically clear themselves to logic zero after a pre-determined amount of time without any further sta access. the sc bits have a default value of logic zero and are triggers to begin execution of a function. when the sta writes a logic on e to an sc bit, the ics 1893cf begins executing the function assigned to that bit. after the ics1893cf co mpletes executing the functi on, it clears the bit to indicate that the action is complete.
ics1893cf, rev. f, 03/01/07 mar. 2007 46 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.2 register 0: control register table 7-5 lists the bits for the control register, a 16-bit r egister used to establish the basic operating modes of the ics1893cf. ? the control register is accessible through the mii management interface. ? its operation is independent of the mac interface configuration. ? it is fully compliant with the iso/ iec control register definition. note: for an explanation of acronyms used in table 7-5 , see chapter 1, ?abbreviat ions and acronyms? . ? whenever the phy address of table 7-16 : ? is equal to 00000 (binary), the isolate bit 0.10 is logic one. ? is not equal to 00000, the is olate bit 0.10 is logic zero. ? as per the ieee std 802. 3u, during any write operat ion to any bit in this register, the sta mu st write the default value to all reserved bits. 7.2.1 reset (bit 0.15) this bit controls the software reset function. setting this bit to logic one initiates an ics1893cf software reset during which all management registers are set to their default values and all internal state machines are set to their idle state. for a detailed description of the software reset process, see section 4.1.2.3, ?software reset? . during reset, the ics1893cf leaves bit 0.15 set to logic one and isolates all sta management register accesses. however, the reset process is not complete until bit 0.15 (a self-clearing bit), is set to logic zero, which indicates the reset process is terminated. table 7-5. control register (register 0 [0x00] bit definition when bit = 0 when bit = 1 ac- cess sf de- fault hex 0.15 reset no effect ics1893cf enters reset mode r/w sc 0 3 0.14 loopback enable disable loopback mode enable loopback mode r/w ? 0 0.13 data rate select 10 mbps operation 100 mbps operation r/w ? 1 0.12 auto-negotiation enable disable auto-negotiation enable auto-negotiation r/w ? 1 0.11 low-power mode normal power mode low-power mode r/w ? 0 0/4? 0.10 isolate no effect isolate ics1893cf from mii r/w ? 0/1? 0.9 auto-negotiation restart no effect restart auto-negotiation r/w sc 0 0.8 duplex mode half-duplex operation full-duplex operation r/w ? 0 0.7 collision test no effect enable collision test r/w ? 0 0 0.6 ieee reserved always 0 n/a ro ? 0? 0.5 ieee reserved always 0 n/a ro ? 0? 0.4 ieee reserved always 0 n/a ro ? 0? 0.3 ieee reserved always 0 n/a ro ? 0? 0 0.2 ieee reserved always 0 n/a ro ? 0? 0.1 ieee reserved always 0 n/a ro ? 0? 0.0 ieee reserved always 0 n/a ro ? 0?
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 47 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.2.2 loopback enable (bit 0.14) this bit controls the loopback mode for th e ics1893cf. setting this bit to logic: ? zero disables the loopback mode. ? one enables the loopback mode by disabling the twis ted-pair transmitter, t he twisted-pair receiver, and the collision detection circuitry. (the sta can override the ics1893cf fr om disabling the collision detection circuitry in loopback mode by writing logic one to bit 0.7.) when the ics1893cf is in loopback mode, the data presented at the mac transmit interface is internally looped back to the mac receive interface. the delay from the assertion of transmit data enable (txen) to the assertion of receive data valid (rxdv) is less than 512 bit times. 7.2.3 data rate select (bit 0.13) this bit provides a means of cont rolling the ics1893cf data rate. its operation depends on the state of several other functions, including the hw/sw input pi n and the auto-negotiation enable bit (bit 0.12). when the ics1893cf is configured for: ? hardware mode (that is, th e hw/sw pin is logic zero), the ics1893cf isolates this bit 0.13 and uses the 10/100sel input pin to establish the data rate for the ics1893cf. in this hardware mode: ? bit 0.13 is undefined. ? the ics1893cf provides a data rate status bi t (in the quickpoll detailed status register, bit 17.15), which always shows the setting of an active link. ? software mode (that is, the hw/sw pin is logic one), the function of bit 0.13 depends on the auto-negotiation enable bit 0.12. when the auto-negotiation sublayer is: ? enabled, the ics1893cf isolates bit 0.13 and relies on the results of the auto-negotiation process to establish the data rate. ? disabled, bit 0.13 determines the data rate. in this case, setting bit 0.13 to logic: ? zero selects 10-mbps ics1893cf operations. ? one selects 100-mbps ics1893cf operations. 7.2.4 auto-negotiation enable (bit 0.12) this bit provides a means of controlling the ics18 93cf auto-negotiation sublay er. its operation depends on the hw/sw input pin. when the ics1893cf is configured for: ? hardware mode, (that is, the hw/sw pin is logic zero ), the ics1893cf isolates bit 0.12 and uses the ansel (auto-negotiation select) input pin to determine whether to enable the auto-negotiation sublayer. note: in hardware mode, bit 0.12 is undefined. ? software mode, (that is, the hw/sw pin is logic one), bit 0.12 determines whether to enable the auto-negotiation sublayer. when bit 0.12 is logic: ? zero: ? the ics1893cf disables the auto-negotiation sublayer. ? the ics1893cf bit 0.13 (the data rate bit) and bit 0.8 (the duplex mode bit) determine the data rate and the duplex mode. ? one: ? the ics1893cf enables the auto-negotiation sublayer. ? the ics1893cf isolates bit 0.13 and bit 0.8.
ics1893cf, rev. f, 03/01/07 mar. 2007 48 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.2.5 low power mode (bit 0.11) this bit provides one way to control the ics1893c f low-power mode function. when bit 0.11 is logic: ? zero, there is no impact to ics1893cf operations. ? one, the ics1893cf enters the low-power mode. in this case, the ics1893cf disables all internal functions and drives all mac output pins low except for those that support the mii serial management port. in addition, the ics1893cf internally activate s the tptri function to tri-state the signals on the twisted-pair transmit pins (tp_txp and tp_t xn) and achieve additi onal power savings. note: there are two ways the ics1893cf can enter low-power mode. when entering low-power mode: ? by setting bit 0.11 to logic one, the ics1893cf maintains the value of all management register bits except the latching high (lh) and latching low (ll) status bits, which are re-initialized to their default values instead. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) ? during a reset, the ics1893cf sets all manageme nt register bits to their default values. 7.2.6 isolate (bit 0.10) this bit controls the ics1893cf isolat e function. when bit 0.10 is logic: ? zero, there is no impact to ics1893cf operations. ? one, the ics1893cf electrically isolates its data paths from the ma c interface. the ics1893cf places all mac output signals (txclk, rxclk, rxdv, rxer , rxd[3:0], col, and crs) in a high-impedance state and it isolates all mac input signals (txd[3:0], txen, and txer). in this mode, the serial management interface continues to operate normally (t hat is, bit 0.10 does not affect the management interface). the default value for bit 0.10 depends upon the phy address of table 7-16 . if the phy address: ? is equal to 00000b, then the default value of bit 0.10 is logic one, and the ics1893cf isolates itself from the mac interface. ? is not equal to 00000b, then the default value of bit 0.10 is logic zero, and the ics1893cf does not isolate its mac interface. 7.2.7 restart auto-negotiation (bit 0.9) this bit allows an sta to restart the auto-negotiation process in software mode (that is, the hw/sw pin is logic one). when bit 0.12 is logic: ? zero, the auto-negotiation sublayer is disabled, an d the ics1893cf isolates any attempt by the sta to set bit 0.9 to logic one. ? one (as set by an sta), the ics1893cf restar ts the auto-negotiation process. once the auto-negotiation process begins, the ics1893cf auto matically sets this bit to logic zero, thereby providing the self-clearing feature.
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 49 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.2.8 duplex mode (bit 0.8) this bit provides a means of controlling the ics18 93cf duplex mode. its oper ation depends on several other functions, including the hw/sw input pin and the auto-negotiation enable bit (bit 0.12). when the ics1893cf is configured for: ? hardware mode (that is, the hw/sw pin is logic zero), the ics1893cf isolates bit 0.8 and uses the dpxsel input pin to establish t he duplex mode for the ics1893cf. in th is hardware mode: ? bit 0.8 is undefined. ? the ics1893cf provides a duplex mode status bit (in the quickpoll detailed status register, bit 17.14), which always shows the setting of an active link. ? software mode (that is, the hw/sw pin is logic one), the function of bit 0.8 depends on the auto-negotiation enable bit, 0.12. w hen the auto-negotiation process is: ? enabled, the ics1893cf isolates bit 0.8 and relies upon the results of the auto-negotiation process to establish the duplex mode. ? disabled, bit 0.8 determines the duplex mode. setting bit 0.8 to logic: ? zero selects half-duplex operations. ? one selects full-duplex operations. (when the ic s1893cf is operating in loopback mode, it isolates bit 0.8, which has no effect on the operation of the ics1893cf.) 7.2.9 collision test (bit 0.7) this bit controls the ics1893cf collision test function. wh en an sta sets bit 0.7 to logic: ? zero, the ics1893cf disables the collis ion detection circuitry for the collis ion test function. in this case, the col signal does not track the txen signal. (the default value for this bit is logic zero, that is, disabled.) ? one, as per the iso/iee 8802-3 standard, clause 22.2.4.1.9, th e ics1893cf enables the collision detection circuitry for the collision te st function, even if the ics1893cf is in loopback mode (that is, bit 0.14 is set to 1). in th is case, the collision test function trac ks the collision detect signal (col) in response to the txen signal. the ics1893cf asserts the collision signal (col) within 512 bit times of receiving an asserted txen signal, and it de-assert s col within 4 bit times of the de-assertion of the txen signal. 7.2.10 ieee reserved bits (bits 0.6:0) the ieee reserves these bits for future use. when an sta: ? reads a reserved bit, the ics1893cf returns a logic zero. ? writes to a reserved bit, it must use the default value specified in this data sheet. the ics1893cf uses some reserved bi ts to invoke auxiliary functions. to ensure proper operation of the ics1893cf, an sta must maintain the default value of these bits. therefore, ics recommends that during any sta write operation, an sta write the default value to all reserved bits, even those bits that are read only.
ics1893cf, rev. f, 03/01/07 mar. 2007 50 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.3 register 1: status register table 7-6 lists the status register bits. these 16 bits of data provide an interfac e between the ics1893cf and an sta. there are two types of status bits: some report the capabilities of th e port, and some indicate the state of signals used to monitor internal circuits. the sta accesses the status register using the serial management interface. during a reset, the ics1893cf initializes the st atus register bits to pre-defined, default values. note: for an explanation of acronyms used in table 7-5 , see chapter 1, ?abbreviat ions and acronyms? . ? as per the ieee std 802. 3u, during any write operat ion to any bit in this register, the sta mu st write the default value to all reserved bits. 7.3.1 100base-t4 (bit 1.15) the sta reads this bit to learn if the ics1893cf can support 100base-t4 operations. bit 1.15 of the ics1893cf is permanently set to logic zero, whic h informs an sta that the ics1893cf cannot support 100base-t4 operations. table 7-6. status register (register 1 [0x01]) bit definition when bit = 0 when bit = 1 ac- cess sf de- fault hex 1.15 100base-t4 always 0. (not supported.) n/a ro ? 0 7 1.14 100base-tx full duplex mode not supported mode supported cw ? 1 1.13 100base-tx half duplex mode not supported mode supported cw ? 1 1.12 10base-t full duplex mode not supported mode supported cw ? 1 1.11 10base-t half duplex mode not supported mode supported cw ? 1 8 1.10 ieee reserved always 0 n/a cw ? 0? 1.9 ieee reserved always 0 n/a cw ? 0? 1.8 ieee reserved always 0 n/a cw ? 0? 1.7 ieee reserved always 0 n/a cw ? 0? 0 1.6 mf preamble suppression phy requires mf preambles phy does not require mf preambles ro ? 0 1.5 auto-negotiation complete auto-negotiation is in process, if enabled auto-negotiation is completed ro lh 0 1.4 remote fault no remote fault detected remote fault detected ro lh 0 1.3 auto-negotiation ability n/a always 1: phy has auto-negotiation ability ro ? 1 9 1.2 link status link is invalid/down link is valid/established ro ll 0 1.1 jabber detect no jabber condition jabber condition detected ro lh 0 1.0 extended capability n/a always 1: phy has extended capabilities ro ? 1
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 51 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.3.2 100base-tx full duplex (bit 1.14) the sta reads this bit to learn if the ics1893cf can support 100base-tx, full-duplex operations. the iso/iec specification requires that the ics1893cf must set bit 1.14 to logic: ? zero if it cannot support 100base-tx, full-duplex operations. ? one if it can support 100base-tx, full-duplex operations. (for the ics1893cf, the default value of bit 1.14 is logic one, in that the ics1893cf supports 100base-tx, full-duplex operations.) bit 1.14 is a command override write bi t, which allows an sta to alter the default value of this bit. [see the description of bit 16.15, the command override write enable bit, in section 7.11, ?register 16: extended control register? .] 7.3.3 100base-tx half duplex (bit 1.13) the sta reads this bit to learn if the ics1893cf can support 100base-tx, half-duplex operations. the iso/iec specification requires that the ics1893cf must set bit 1.13 to logic: ? zero if it cannot support 100b ase-tx, half-duplex operations. ? one if it can support 100base-tx, half-duplex operations. (for the ics1893cf, the default value of bit 1.13 is logic one. therefore, when an sta reads the status register, the sta is informed that the ics1893cf supports 100base-tx , half-duplex operations.) this bit 1.13 is a command override write bit, which a llows an sta to alter the default value of this bit. [see the description of bit 16.15, the command override write enable bit, in section 7.11, ?register 16: extended control register? .] 7.3.4 10base-t full duplex (bit 1.12) the sta reads this bit to learn if the ics1893cf can support 10base-t, full-duplex operations. the iso/iec specification requires that the ics1893cf must set bit 1.12 to logic: ? zero if it cannot support 10base-t, full-duplex operations. ? one if it can support 10base-t, full-duplex operations . (for the ics1893cf, the default value of bit 1.12 is logic one. therefore, when an sta reads the stat us register, the sta is informed that the ics1893cf supports 10base-t, full-duplex operations.) this bit 1.12 is a command override write bit, which a llows an sta to alter the default value of this bit. [see the description of bit 16.15, the command override write enable bit, in section 7.11, ?register 16: extended control register? .] 7.3.5 10base-t half duplex (bit 1.11) the sta reads this bit to learn if the ics1893cf can support 10base-t, half-duplex operations. the iso/iec specification requires that the ics1893cf must set bit 1.11 to logic: ? zero if it cannot support 10base-t, half-duplex operations. ? one if it can support 10base-t, half-duplex operations . (for the ics1893cf, the default value of bit 1.11 is logic one. therefore, when an sta reads the stat us register, the sta is informed that the ics1893cf supports 10base-t, half-duplex operations.) bit 1.11 of the ics1893cf status re gister is a command override write bit., which allows an sta to alter the default value of this bit. [see the description of bit 16.15, the command override write enable bit, in section 7.11, ?register 16: extended control register? .]
ics1893cf, rev. f, 03/01/07 mar. 2007 52 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.3.6 ieee reserved bits (bits 1.10:7) the ieee reserves these bits for future use. when an sta: ? reads a reserved bit, the ics1893cf returns a logic zero. ? writes a reserved bit, the sta must use the default value specified in this data sheet. both the iso/iec standard and the ics1893cf reserve the use of some management register bits. ics uses some reserved bits to invoke ics1893cf test functions. to ensure proper operation of the ics1893cf, an sta must maintain the default value of these bits. therefore, ics recommends that an sta write the default value to all reserved bits during all management register write operations. reserved bits 1.10:7 are command override write (cw) bits. when bit 16.15, the command register override bit, is logic: ? zero, the ics1893cf prevents all sta writes to cw bits. ? one, an sta can modify the value of these bits. 7.3.7 mf preamble suppression (bit 1.6) status register bit 1.6 is the management frame (mf) preamble suppression bit. the ics1893cf sets bit 1.6 to inform the sta of its ability to receive frames that do not have a preamble. when this bit is logic: ? zero, the ics1893cf is indicating it cannot accept frames with a suppressed preamble. ? one, the ics1893cf is indicating it can ac cept frames that do not have a preamble. although the ics1893cf supports management frame preamble suppression, its default value for bit 1.6 is logic zero. this default value ensures that bit 1. 6 is backward comp atible with the ic s1890, which does not have this capability. as the me ans of enabling this feature, the ics1893cf implements bit 1.6 as a command override write bit, instead of as a read-only bit as in the ics1890. an sta uses the bit 1.6 to enable mf preamble suppression in the ics1893cf. [see the description of bit 16.15, the command override write enable bit, in section 7.11, ?register 16: extended control register? .] 7.3.8 auto-negotiation complete (bit 1.5) an sta reads bit 1.5 to determine the state of the ics1893cf auto-negotiation process. the ics1893cf sets the value of this bit using two criter ia. when its auto-negotiation sublayer is: ? disabled, the ics1893cf sets bit 1.5 to logic zero. ? enabled, the ics1893cf sets bit 1.5 to a value based on the state of the auto-negotiation state machine. in this case, it sets bit 1.5 to logic one only upon co mpletion of the auto-negotiation process. this setting indicates to the sta that a link is arbitr ated and the contents of management registers 4, 5, and 6 are valid. for details on the auto-negotiation process, see section 6.2, ?functional block: auto-negotiation? . bit 1.5 is a latching high (lh) bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) note: an auto-negotiation restart does not clear an lh bit. however, performing two consecutive reads of this register provides the present state of the bit.
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 53 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.3.9 remote fault (bit 1.4) an sta reads bit 1.4 to determine if a remote fault exists. the ics1893cf sets bit 1.4 based on the remote fault bit received from its remote link partner. the ics1893cf receives the remote fault bit as part of the link code word exchanged during the auto -negotiation process. if the ics1893cf receives a link code word from its remote link partner and the remote fault bit is set to: ? zero, then the ics1893cf sets bit 1.4 to logic zero. ? one, then the ics1893cf sets bit 1.4 to logic one. in this case, the remote link partner is reporting the detection of a fault, which typically occurs when th e remote link partner is having a problem with its receive channel. bit 1.4 is a latching high status bit. (for more in formation on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) note: the ics1893cf has two versions of the remote fault bit. ? one version of the remote fault bit is a latching high version. an sta can access this version through either management register 1 (bit 1.4) or 17 (bit 17.1). this bit 1.4/17.1 is cleared when an sta reads either of these registers. (bit 1.4 is identical to bit 17.1 in that they are the same internal bit.) ? another version of the remote fault bit is u pdated whenever the ics1893cf receives a new link control word. an sta can access this version through management register 5 (bit 5.13), which like bits 1.4/17.1, also reports the status of the remote fault bit received from the remote link partner. however, bit 5.13 is not a latching high bit. the operation of both bit 1.4/17.1 and bit 5. 13 are in compliance with the ieee std 802.3u. 7.3.10 auto-negotiation ability (bit 1.3) the sta reads bit 1.3 to determine if the ics1893c f can support the auto-negotiation process. if the ics1893cf: ? cannot support the auto-negotiation proc ess, it clears bit 1.3 to logic zero. ? can support the auto-negotiation process, it sets bit 1.3 to logic one. (for the ics1893cf, the default value of bit 1.3 is logic one.) 7.3.11 link status (bit 1.2) the purpose of this bit 1.2 (which is also accessib le through the quickpoll detailed status register, bit 17.0) is to determine if an esta blished link is dropped, even momentarily. to indicate a link that is: ? valid, the ics1893cf sets bit 1.2 to logic one. ? invalid, the ics1893cf clears bit 1.2 to logic zero. this bit is a latching low (ll) bit that the link moni tor function controls. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) the link monitor function continually observes the data received by either its 10base-t or 100base-tx twisted-pair receivers to determine the link status and stores the results in the link status bit. the criterion the link monitor uses to determine if a link is valid or invali d depends on the following: ? type of link ? present link state (valid or invalid) ? presence of any link errors ? auto-negotiation process for more information on the link monitor functi on (relative to the link status bit), see section 6.5.5, ?10base-t operation: link monitor? .
ics1893cf, rev. f, 03/01/07 mar. 2007 54 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.3.12 jabber detect (bit 1.1) the purpose of this bit is to allow an sta to dete rmine if the ics1893cf detects a jabber condition as defined in the iso/iec specification.the ics1893cf ja bber detection function is controlled by the jabber inhibit bit in the 10base-t operations register (bit 18.5). to detect a jabber condition, first the ics1893cf jabber detection function must be enabled. when bit 18.5 is logic: ? zero, the ics1893cf disables jabber detection an d sets the jabber dete ct bit to logic zero. ? one, the ics1893cf enables jabber detection and sets the jabber detect bit to logic one upon detection of a jabber condition. when no jabber co ndition is detected, the jabber detect bit is not altered. note: 1. the jabber detect bit is accessible through both the status register (as bit 1.1) and the quickpoll detailed status register (as bit 17.2). a read of either register clears the jabber detect bit. 2. the jabber detect bit is a latching high (lh) bit. (f or more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) 7.3.13 extended capability (bit 1.0) the sta reads bit 1.0 to determine if the ics1893cf ha s an extended register set. in the ics1893cf this bit is always logic one, indicating that it has extended registers.
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 55 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.4 register 2: phy identifier register table 7-7 lists the bits for phy identifier register (register 2), which is one of two phy identifier registers that are part of a set defined by the iso/iec specificat ion. as a set, the phy identifier registers (registers 2 and 3) include a unique, 32-bit phy identifier composed from the following: ? organizationally unique identifier (oui), discussed in this section ? manufacturer?s phy model number, discussed in section 7.5, ?register 3: phy identifier register? ? manufacturer?s phy revision number, discussed in section 7.5, ?register 3: phy identifier register? all of the bits in the two phy identifier registers ar e command override write bits. an sta can read them at any time without condition. howe ver, an sta can modify these register bits only when the command register override bit (bit 16.15) is enabled with a logic one. note: for an explanation of acronyms used in table 7-5 , see chapter 1, ?abbreviat ions and acronyms? . table 7-7. phy identifier register (register 2 [0x02]) bit definition when bit = 0 when bit = 1 access special function default hex 2.15 oui bit 3 | c n/a n/a cw ? 0 0 2.14 oui bit 4 | d n/a n/a cw ? 0 2.13 oui bit 5 | e n/a n/a cw ? 0 2.12 oui bit 6 | f n/a n/a cw ? 0 2.11 oui bit 7 | g n/a n/a cw ? 0 0 2.10 oui bit 8 | h n/a n/a cw ? 0 2.9 oui bit 9 | i n/a n/a cw ? 0 2.8 oui bit 10 | j n/a n/a cw ? 0 2.7 oui bit 11 | k n/a n/a cw ? 0 1 2.6 oui bit 12 | l n/a n/a cw ? 0 2.5 oui bit 13 | m n/a n/a cw ? 0 2.4 oui bit 14 | n n/a n/a cw ? 1 2.3 oui bit 15 | o n/a n/a cw ? 0 5 2.2 oui bit 16 | p n/a n/a cw ? 1 2.1 oui bit 17 | q n/a n/a cw ? 0 2.0 oui bit 18 | r n/a n/a cw ? 1
ics1893cf, rev. f, 03/01/07 mar. 2007 56 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. ieee-assigned organizationally unique identifier (oui) for each manufacturing organization, the ieee assign s an 3-octet oui. for integrated circuit systems, inc. the ieee-assigned 3-octet oui is 00a0beh. this oui is retained for backwards comp atibility with older versions of the ics1893. the binary representation of an oui is formed by ex pressing each octet as a sequence of eight bits, from least significant to most signif icant, and from left to right. table 7-8 provides the iso/iec-defined mapping of the oui (in ieee std. 802-1990 form at) to management registers 2 and 3. 7.5 register 3: phy identifier register table 7-9 lists the bits for phy identifier register (register 3), which is one of two phy identifier registers that are part of a set defined by the iso/iec sp ecification. this regist er stores the following: ? part of the oui [see the text in section 7.4, ?register 2: phy identifier register? ] ? manufacturer?s phy model number ? manufacturer?s phy revision number all the bits in the two phy identifi er registers are command override write bits. an sta can read them at any time without condition. however, an sta can modify these register bits only when the command register override bit (bit 16.15) is enabled with a logic one. note: for an explanation of acronyms used in table 7-5 , see chapter 1, ?abbreviat ions and acronyms? . table 7-8. ieee-assigned organization ally unique identifier first octet second octet third octet 000ae b abcdefghi jklmnopqrstuvwx 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 000000000000 01010111110 1 0015f1 2.15:12 2.11:8 2.7:4 2.3:0 3.15:12 3.11:10 register 2 register 3 table 7-9. phy identifier register (register 3 [0x03]) bit definition when bit = 0 when bit = 1 access special function default hex 3.15 oui bit 19 | s n/a n/a cw ? 1 f 3.14 oui bit 20 | t n/a n/a cw ? 1 3.13 oui bit 21 | u n/a n/a cw ? 1 3.12 oui bit 22 | v n/a n/a cw ? 1
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 57 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.5.1 oui bits 19-24 (bits 3.15:10) the most-significant 6 bits of regist er 3 (that is, bits 3.15:10) include oui bits 19 through 24. oui bit 19 is stored in bit 3.15, while oui bit 24 is stored in bit 3.10. 7.5.2 manufacturer's model number (bits 3.9:4) the model number for the ics1893cf is 5 (dec imal). it is stored in bit 3.9:4 as 00101b. 7.5.3 revision number (bits 3.3:0) table 7-10 lists the valid ics1893cf revision numbers, which are 4-bit binary numbers stored in bits 3.3:0. 3.11 oui bit 23 | w n/a n/a cw ? 0 4 3.10 oui bit 24 | x n/a n/a cw ? 1 3.9 manufacturer?s model number bit 5 n/a n/a cw ? 0 3.8 manufacturer?s model number bit 4 n/a n/a cw ? 0 3.7 manufacturer?s model number bit 3 n/a n/a cw ? 0 4 3.6 manufacturer?s model number bit 2 n/a n/a cw ? 1 3.5 manufacturer?s model number bit 1 n/a n/a cw ? 0 3.4 manufacturer?s model number bit 0 n/a n/a cw ? 1 3.3 revision number bit 3 n/a n/a cw ? 0 2 3.2 revision number bit 2 n/a n/a cw ? 0 3.1 revision number bit 1 n/a n/a cw ? 0 3.0 revision number bit 0 n/a n/a cw ? 0 table 7-10. ics1893cf revision number decimal bits 3.3:0 description 2 0000 idt 1893c table 7-9. phy identifier register (register 3 [0x03]) bit definition when bit = 0 when bit = 1 access special function default hex
ics1893cf, rev. f, 03/01/07 mar. 2007 58 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.6 register 4: auto-negotiation register table 7-11 lists the bits for the auto-nego tiation register. an sta uses this register to select the ics1893cf capabilities that it wants to advertise to its remote link pa rtner. during the auto-negotiation process, the ics1893cf advertises (t hat is, exchanges) capab ility data with its remote link partner by using a pre-defined link code word. the link code word is embedded in the fast link pulses exchanged between phys when the ics1893cf has its auto-negotiation sublayer enabled. the value of the link control word is established based on the value of the bits in this register. note: for an explanation of acronyms used in table 7-5 , see chapter 1, ?abbreviat ions and acronyms? . ? as per the ieee std 802. 3u, during any write operat ion to any bit in this register, the sta mu st write the default value to all reserved bits. 7.6.1 next page (bit 4.15) this bit indicates whether the ics1893cf uses the next page mode functions during the auto-negotiation process. if bit 4.15 is logic: ? zero, then the ics1893cf indicates to its remote link partner that thes e features are disabled. (although the default value of this bit is logic zero, the ics1893cf does support the next page function.) ? one, then the ics1893cf advertises to its remo te link partner that this feature is enabled. table 7-11. auto-negotiation advertisement register (register 4 [0x04]) bit definition when bit = 0 when bit = 1 ac- cess sf de- fault hex 4.15 next page next page not supported next page supported r/w ? 0 0 4.14 ieee reserved always 0 n/a cw ? 0? 4.13 remote fault locally, no faults detected local fault detected r/w ? 0 4.12 ieee reserved always 0 n/a cw ? 0? 4.11 ieee reserved always 0 n/a cw ? 0? 1 4.10 ieee reserved always 0 n/a cw ? 0? 4.9 100base-t4 always 0. (not supported.) n/a cw ? 0 4.8 100base-tx, full duplex do not advertise ability advertise ability r/w ? 1 4.7 100base-tx, half duplex do not advertise ability advertise ability r/w ? 1 e 4.6 10base-t, full duplex do not adver tise ability advertise ability r/w ? 1 4.5 10base-t half duplex do not adverti se ability advertise ability r/w ? 1 4.4 selector field bit s4 ieee 802.3-specifi ed default n/a cw ? 0 4.3 selector field bit s3 ieee 8 02.3-specified default n/a cw ? 0 1 4.2 selector field bit s2 ieee 802.3-specifi ed default n/a cw ? 0 4.1 selector field bit s1 ieee 802.3-specifi ed default n/a cw ? 0 4.0 selector field bit s0 n/a ieee 802.3-specified default cw ? 1
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 59 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.6.2 ieee reserved bit (bit 4.14) the iso/iec specification reserves this bit for future use. however, the iso/iec standard also defines bit 4.14 as the acknowledge bit. when this reserved bit is read by an sta, the ics 1893cf returns a logic zero. however, whenever an sta writes to this reserved bit, it must use the default value specified in this data sheet. ics uses some reserved bits to invoke auxiliary functions. to ensure proper operat ion of the ics1893cf, an sta must maintain the default value of these bits. therefore, ics recommends that an sta always write the default value of any reserved bits during all management register write operations. reserved bit 4.14 is a command override write (cw) bit. whenever bit 16.15 (the command register override bit) is logic: ? zero, the ics1893cf isolates all sta writes to bit 4.14. ? one, an sta can modify the value of bit 4.14. 7.6.3 remote fault (bit 4.13) when the ics1893cf auto-negotiation sublayer is enabled, the ics1893cf transmits the remote fault bit 4.13 to its remote link partner during the auto-negotiation process. the remote fault bit is part of the link code word that the ics1893cf exchanges with its remote link partner. the ics1893cf sets this bit to logic one whenever it detects a problem with th e link, locally. the data in this re gister is sent to the remote link partner to inform it of the potentia l problem. if the ics1893cf does not dete ct a link fault, it clears bit 4.13 to logic zero. whenever the ics1893cf: ? does not detect a link fault, the ics189 3cf clears bit 4.13 to logic zero. ? detects a problem with the link, during the auto-negotiation process, this bit is se t. as a result, the data on this bit is sent to the remote link partner to inform it of the potential problem. 7.6.4 ieee reserved bits (bits 4.12:10) the ieee reserves these bits for future use. when an sta: ? reads a reserved bit, the ics1893cf returns a logic zero. ? writes to a reserved bit, it must use the default value specified in this data sheet. the ics1893cf uses some reserved bi ts to invoke auxiliary functions. to ensure proper operation of the ics1893cf, an sta must maintain the default value of these bits. therefore, ics recommends that during any sta write operation, an sta write the default value to all reserved bits, even those bits that are read only.
ics1893cf, rev. f, 03/01/07 mar. 2007 60 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.6.5 technology ability field (bits 4.9:5) when its auto-negotiation sublayer is enabled, the ics1893cf transmits its link capabilities to its remote link partner during the auto-negotiation process. the technology ability field (taf) bits 4.12:5 determine the specific abilities that the ics1893cf advert ises. the iso/iec specification defines the taf technologies in annex 28b. the iso/iec specification reserves bits 4.12:10 for future use. when each of these reserved bits is: ? read by an sta, the ics1893cf returns a logic zero ? written to by an sta, the sta must use the default value specified in this data sheet ics uses some reserved bits to invo ke auxiliary functions. to ensure proper operation of the ics1893cf, an sta must maintain the default value of these bits. therefore, ics recommends that an sta always write the default value of any reserved bits during all management register write operations. reserved bits 4.12:10 are command override write (cw) bits. whenever bit 16.15 (the command register override bit) is logic: ? zero, the ics1893cf isolates all sta writ es to cw bits, including bits 4.12:10. ? one, an sta can modify the value of bits 4.12:10 each of the bits 4.9:5 in the taf r epresent a specific technology capabilit y. when one of these bits is logic: ? zero, it indicates to the remote link partner th at the local device cannot support the technology represented by the bit. ? one, it indicates to the remote link partner that the local device can support the technology. with the exception of bit 4.9, the default settings of the taf bits depend on the ics1893cf operating mode. bit 4.9 is always logic zero, indicating that the ics1893cf cannot support 100base-t4 operations. the taf bits are command override write bits. the default value of these bits depends on the signal level on the hw/sw pin and whether the auto-negotiation sublayer is enabled. with the auto-negotiation enable bit (bit 0.12) set to logic: ? zero (that is, disabled), the ics1893cf does not exec ute the auto-negotiation process. upon completion of the initialization sequence, the ics1893cf proceeds to the idle stat e and begins transmitting idles. two control register bits ? the data rate select bi t (bit 0.13) and the duplex select bit (bit 0.8) ? determine the technology mode that the ics1893cf uses for data transmission and reception. in this mode, the values of the taf bits (bits 4.8:5) are undefined. ? one (that is, enabled), the ics1893cf executes th e auto-negotiation process and advertises its capabilities to the remote link partner. the taf bits (bits 4.8:5) determine the capabilities that the ics1893cf advertises to its remote link partner. for the ics1893cf, all of these bits 4.8:5 are set to logic one, indicating the ability of the ics1893cf to provide these technologies. note: 1. the ics1893cf does not alter the value of the status register bits based on the taf bits in register 4, as the iso/iec definitions for the status register bits require these bits to indicate all the capabilities of the ics1893cf. 2. the sta can alter the default taf bit settings, 4. 12:5, and subsequently is sue an auto-negotiation restart. 7.6.6 selector field (bits 4.4:0) when its auto-negotiation sublayer is enabled, the ic s1893cf transmits it s link capabilities to its remote link partner during the auto-negotiation process. the selector field is transmitted based on the value of bits 4.4:0. these bits indicate to the remote link partner the type of message being sent during the auto-negotiation proc ess. the ics1893cf su pports ieee std. 802. 3, represented by a value of 00001b in bits 4.4:0. the iso/iec 8802-3 standard defines the selector field technologies in annex 28a.
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 61 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.7 register 5: auto-negotiation link partner ability register table 7-12 lists the bits for the auto-negot iation link partner ability register . an sta uses this register to determine the capabilities being advert ised by the remote link partner. du ring the au to-negotiation process, the ics1893cf advertises (that is, exchanges) the capability data wit h its remote link partner using a pre-defined link code word. the value of the link control word received from its remote link partner establishes the value of the bits in this register. note: 1. for an explanation of acronyms used in table 7-12 , see chapter 1, ?abbreviations and acronyms? . 2. the values in this register are valid only when the auto-negotiation process is complete, as indicated by bit 1.5 or bit 17.4. ? as per the ieee std 802. 3u, during any write operat ion to any bit in this register, the sta mu st write the default value to all reserved bits. 7.7.1 next page (bit 5.15) if bit 5.15 is logic: ? zero, then the remote link partner is indicating that this is the last page being transmitted. ? one, then the remote link partner is indicating that additional pages follow. table 7-12. auto-negotiation link partner ability register (register 5 [0x05]) bit definition when bit = 0 when bit = 1 ac- cess sf de- fault hex 5.15 next page next page disabled next page enabled ro ? 0 0 5.14 acknowledge always 0 n/a ro ? 0 5.13 remote fault no faults detected remote fault detected ro ? 0 5.12 ieee reserved always 0 n/a ro ? 0? 5.11 ieee reserved always 0 n/a ro ? 0? 0 5.10 ieee reserved always 0 n/a ro ? 0? 5.9 100base-t4 always 0. (not supported.) n/a ro ? 0 5.8 100base-tx, full duplex link partner is not capable link partner is capable ro ? 0 5.7 100base-tx, half duplex link partner is not capable link partner is capable ro ? 0 0 5.6 10base-t, full duplex link partner is not capable link partner is capable ro ? 0 5.5 10base-t, half duplex link partner is not capable link partner is capable ro ? 0 5.4 selector field bit s4 ieee 802.3 defined. always 0. n/a ro ? 0 5.3 selector field bit s3 ieee 802.3 defined. always 0. n/a cw ? 0 0 5.2 selector field bit s2 ieee 802.3 defined. always 0. n/a cw ? 0 5.1 selector field bit s1 ieee 802.3 defined. always 0. n/a cw ? 0 5.0 selector field bit s0 n/a ieee 802.3 defined. always 1. cw ? 0
ics1893cf, rev. f, 03/01/07 mar. 2007 62 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.7.2 acknowledge (bit 5.14) the iso/iec specification defines bit 5.14 as the acknowledge bit. when this bit is a: ? zero, it indicates that the remote link partner has not received the ics1893cf link control word. ? one, it indicates to the ics1893cf / sta that the remote link partner has acknowledged reception of the ics1893cf link control word. 7.7.3 remote fault (bit 5.13) the iso/iec specification defines bit 5.13 as the remote fault bit. this bit is set based on the link control word received from the remote link pa rtner. when this bit is a logic: ? zero, it indicates that the remote link partner detects a link fault. ? one, it indicates to the ics1893cf / sta that the remote link partner detects a link fault. note: for more information about this bit, see section 7.3.9, ?remote fault (bit 1.4)? . 7.7.4 technology ability field (bits 5.12:5) the technology ability field (taf) bits (bits 5.12:5) determine the specific abilit ies that the remote link partner is advertising. these bits are set based upon the link code word receiv ed from the remote link partner during the auto-negotiation process. the is o/iec specification defines the taf technologies in annex 28b. the iso/iec specification reserves bits 5.12:10 for future use. when each of these reserved bits is: ? read by an sta, the ics1893cf returns a logic zero. ? written to by an sta, the sta must use the default value specified in this data sheet. idt uses some reserved bits to invoke auxiliary func tions. to ensure proper op eration of the ics1893cf, an sta must maintain the default value of these bits . therefore, idt recommends that an sta always write the default value of any reserved bits during all management register write operations. 7.7.5 selector field (bits 5.4:0) the selector field bits indicate the technology or encoding that the remote link partner is using for the auto-negotiation messa ge. the ics1893cf supports only ieee std. 802.3, re presented by a value of 00001b in bits 5.4:0. the iso/iec standard defines the selector field technologies in annex 28a. presently, the ieee stand ard defines the follo wing two valid codes: ? 00001b (ieee std 802.3) ? 00010b (ieee std 802.9)
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 63 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.8 register 6: auto-negot iation expansion register table 7-13 lists the bits for the auto-ne gotiation expansion register, which indicates the status of the auto-negotiation process. note: for an explanation of acronyms used in table 7-13 , see chapter 1, ?abbreviations and acronyms? . ? as per the ieee std 802. 3u, during any write operat ion to any bit in this register, the sta mu st write the default value to all reserved bits. 7.8.1 ieee reserved bits (bits 6.15:5) the iso/iec specification reserves thes e bits for future use. when an sta: ? reads a reserved bit, the ics1893cf returns a logic zero. ? writes to a reserved bit, the sta must use t he default value specified in this data sheet. ics uses some reserved bits to invo ke auxiliary functions. to ensure proper operation of the ics1893cf, an sta must maintain the default value of these bits . therefore, idt recommends that an sta always write the default value of any reserved bits during all management register write operations. reserved bits 5.15:5 are command override write (c w) bits. when the command register override bit (bit 16.15) is logic: ? zero, the ics1893cf isolates all sta writes to cw bits. ? one, an sta can modify the value of these bits table 7-13. auto-negotiation expansion re gister (register 6 [0x06]) bit definition when bit = 0 when bit = 1 ac- cess sf de- fault hex 6.15 ieee reserved always 0 n/a cw ? 0? 0 6.14 ieee reserved always 0 n/a cw ? 0? 6.13 ieee reserved always 0 n/a cw ? 0? 6.12 ieee reserved always 0 n/a cw ? 0? 6.11 ieee reserved always 0 n/a cw ? 0? 0 6.10 ieee reserved always 0 n/a cw ? 0? 6.9 ieee reserved always 0 n/a cw ? 0? 6.8 ieee reserved always 0 n/a cw ? 0? 6.7 ieee reserved always 0 n/a cw ? 0? 0 6.6 ieee reserved always 0 n/a cw ? 0? 6.5 ieee reserved always 0 n/a cw ? 0? 6.4 parallel detection fault no fault multiple technologies detected ro lh 0 6.3 link partner next page able link partner is not next page able link partner is next page able ro ? 0 4 6.2 next page able local device is not next page able local device is next page able ro ? 1 6.1 page received next page not received next page received ro lh 0 6.0 link partner auto-negotiation able link partner is not auto-negotiation able link partner is auto-negotiation able ro ? 0
ics1893cf, rev. f, 03/01/07 mar. 2007 64 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.8.2 parallel detection fault (bit 6.4) the ics1893cf sets this bit to a logic one if a paralle l detection fault is encount ered. a parallel detection fault occurs when the ics1893cf cannot disseminate th e technology being used by its remote link partner. bit 6.4 is a latching high (lh) status bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) 7.8.3 link partner next page able (bit 6.3) bit 6.3 is a status bit that report s the capabilities of the remote link partner to support the next page features of the auto-negotiation process. the ics1893cf sets this bit to a logi c one if the remote link partner sets the next page bit in its link control word. 7.8.4 next page able (bit 6.2) bit 6.2 is a status bit that reports the capabilities of the ics1893cf to support the next page features of the auto-negotiation process. the ics1893cf sets this bit to a logic one to indicate that it can support these features. 7.8.5 page received (bit 6.1) the ics1893cf sets its page received bit to a logic one whenever a new link control word is received and stored in its auto-negoti ation link partner ability register. the page received bit is cleared to logic zero on a read of the auto-negotiation expansion register. bit 6.1 is a latching high (lh) status bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) 7.8.6 link partner auto-negotiation able (bit 6.0) if the ics1893cf: ? does not receive fast link pulse bursts from its re mote link partner, then this bit remains a logic zero. ? receives valid flp bursts from its remote link partner (thereby indicating that it can participate in the auto-negotiation process), then the ics1893cf sets this bit to a logic one.
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 65 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.9 register 7: auto-negotiation next page transmit register table 7-14 lists the bits for the auto-ne gotiation next page transmit register, which establishes the contents of the next page link control word that is transmitted during next page operations. this table is compliant with the is o/iec specification. note: for an explanation of acronyms used in table 7-14 , see chapter 1, ?abbreviations and acronyms? . ? as per the ieee std 802. 3u, during any write operat ion to any bit in this register, the sta mu st write the default value to all reserved bits. table 7-14. auto-negotiation next page transmit register (register 7 [0x07]) bit definition when bit = 0 when bit = 1 ac- cess sf de- fault hex 7.15 next page last page additional pages follow rw ? 0 2 7.14 ieee reserved always 0 n/a ro ? 0? 7.13 message page unformatted page message page rw ? 1 7.12 acknowledge 2 cannot comply with message can comply with message rw ? 0 7.11 toggle previous link code word was zero previous link code word was one ro ? 0 0 7.10 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message rw ? 0 7.9 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message rw ? 0 7.8 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message rw ? 0 7.7 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message rw ? 0 0 7.6 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message rw ? 0 7.5 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message rw ? 0 7.4 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message rw ? 0 7.3 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message rw ? 0 1 7.2 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message rw ? 0 7.1 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message rw ? 0 7.0 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message rw ? 1
ics1893cf, rev. f, 03/01/07 mar. 2007 66 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.9.1 next page (bit 7.15) this bit is used by a phy/sta to enable the transm ission of next pages following the base link control word as long as the remote link partner suppor ts the next page features of auto-negotiation. this bit is used to establish the state of the next page (np) bit of the next page link control word (that is, the np bit of the next page link co ntrol word tracks this bit). during a next page exchange, if the np bit is logic: ? zero, it indicates to the remote link partne r that this is the last message or page. ? one, it indicates to the re mote link partner that additio nal pages follow this message. 7.9.2 ieee reserved bit (bit 7.14) the iso/iec specification reserves this bit fo r future use. when th is reserved bit is: ? read by an sta, the ics1893cf returns a logic zero. ? written to by an sta, the sta must use the default value specified in this data sheet. idt uses some reserved bits to invoke auxiliary func tions. to ensure proper op eration of the ics1893cf, an sta must maintain the default value of these bits . therefore, idt recommends that an sta always write the default value of any reserved bits during all management register write operations. 7.9.3 message page (bit 7.13) the message page (mp) bit (bit 7.13) is used to determine the format or type of page being transmitted. the value of this bit establishes the state of t he mp bit in the next page link control word. if this bit is set to logic: ? zero, it indicates that the page is an unformatted page. ? one, it indicates to the remote link partner that the page being transmitted is a message page. 7.9.4 acknowledge 2 (bit 7.12) this bit is used to indicate the ability of the ics1893cf to comply with a message. the value of this bit establishes the state of the ack2 bit in the next page link control word. if this bit is set to logic: ? zero, it indicates that the ics189 3cf cannot comply with the message. ? one, it indicates to the remote link partner that the ics1893cf can comply with the message. 7.9.5 toggle (bit 7.11) the toggle (t) bit (bit 7.11) is used to synchroniz e the transmission of ne xt page messages with the remote link partner. the value of this bit establishes the state of the to ggle bit in the next page link control word. this bit toggles with each tr ansmitted link control word. if the previous next page link control word toggle bit has a value of logic: ? zero, then the toggle bit is set to logic one. ? one, then the toggle bit is set to logic zero. the initial next page link control word toggle bit is set to the inverse of the base link control word bit 11. 7.9.6 message code field / unformatted code field (bits 7.10:0) bits 7.10:0 represent either the message code field m[ 10:0] or the unformatted code field u[10:0] bits. the value of these bits establish the state of the m[10:0] / u[10:0] bits in the next page link control word.
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 67 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.10 register 8: auto-ne gotiation next page link partner ability register table 7-15 lists the bits for the auto-negotiation next page link partner ability register, which establishes the contents of the next page link control word th at is transmitted during next page operations. this table is compliant with t he iso/iec specification. note: for an explanation of acronyms used in table 7-15 , see chapter 1, ?abbreviations and acronyms? . ? as per the ieee std 802. 3u, during any write operat ion to any bit in this register, the sta mu st write the default value to all reserved bits. table 7-15. auto-negotiation ne xt page link part ner ability register (register 8 [0x08]) bit definition when bit = 0 when bit = 1 ac- cess sf de- fault hex 8.15 next page last page additional pages follow ro ? 0 0 8.14 ieee reserved always 0 n/a ro ? 0? 8.13 message page unformatted page message page ro ? 0 8.12 acknowledge 2 cannot comply with message can comply with message ro ? 0 8.11 toggle previous link code word was zero previous link code word was one ro ? 0 0 8.10 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message ro ? 0 8.9 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message ro ? 0 8.8 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message ro ? 0 8.7 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message ro ? 0 0 8.6 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message ro ? 0 8.5 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message ro ? 0 8.4 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message ro ? 0 8.3 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message ro ? 0 0 8.2 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message ro ? 0 8.1 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message ro ? 0 8.0 message code field /unformatted code field bit value depends on the particular message bit value depends on the particular message ro ? 0
ics1893cf, rev. f, 03/01/07 mar. 2007 68 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.10.1 next page (bit 8.15) this bit is used by a phy/sta to enable the transm ission of next pages following the base link control word as long as the remote link partner suppor ts the next page features of auto-negotiation. this bit is used to establish the state of the next page (np) bit of the next page link control word (that is, the np bit of the next page link cont rol word tracks this bit). during a ne xt page exchange, if the np bit is logic: ? zero, it indicates to the remote link partne r that this is the last message or page. ? one, it indicates to the re mote link partner that additio nal pages follow this message. 7.10.2 ieee reserved bit (bit 8.14) the iso/iec specification reserves this bit fo r future use. when th is reserved bit is: ? read by an sta, the ics1893cf returns a logic zero. ? written to by an sta, the sta must use the default value specified in this data sheet. idt uses some reserved bits to invoke auxiliary func tions. to ensure proper op eration of the ics1893cf, an sta must maintain the default value of these bits . therefore, idt recommends that an sta always write the default value of any reserved bits during all management register write operations. 7.10.3 message page (bit 8.13) the message page (mp) bit (bit 8.13) is used to determine the format or type of page being transmitted. the value of this bit establishes the state of t he mp bit in the next page link control word. if this bit is set to logic: ? zero, it indicates that the page is an unformatted page. ? one, it indicates to the remote link partner that the page being transmitted is a message page. 7.10.4 acknowledge 2 (bit 8.12) this bit is used to indicate the ability of the ics1893cf to comply with a message . the value of this bit establishes the state of the ack2 bit in the next page link control word. if this bit is set to logic: ? zero, it indicates that the ics189 3cf cannot comply with the message. ? one, it indicates to the remote link partner that the ics1893cf can comply with the message. if the previous next page link control word toggle bit has a value of logic: ? zero, then the toggle bit is set to logic one. ? one, then the toggle bit is set to logic zero. the initial next page link control word toggle bit is set to the inverse of the base link control word bit 11. 7.10.5 message code field / unformatted code field (bits 8.10:0) bits 8.10:0 represent either the message code field m[ 10:0] or the unformatted code field u[10:0] bits. the value of these bits establish the state of the m[10:0] / u[10:0] bits in the next page link control word.
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 69 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.11 register 16: extended control register table 7-16 lists the bits for the extended control register , which the ics1893cf provides to allow an sta to customize the operations of the device. note: 1. for an explanation of acronyms used in table 7-16 , see chapter 1, ?abbreviations and acronyms? . 2. during any write operation to any bit in this register, the sta must write the default value to all reserved bits. ? the default is the state of this pin at reset. table 7-16. extended control register (register 16 [0x10]) bit definition when bit = 0 when bit = 1 ac- cess sf de- fault hex 16.15 command override write enable disabled enabled rw sc 0 ? 16.14 ics reserved read unspec ified read unspecified rw/0 ? 0 16.13 ics reserved read unspec ified read unspecified rw/0 ? 0 16.12 ics reserved read unspec ified read unspecified rw/0 ? 0 16.11 ics reserved read unspec ified read unspecified rw/0 ? 0 ? 16.10 phy address bit 4 for a detailed explanation of this bit?s operation, see section 5.5, ?status interface? . ro ? p4rd? 16.9 phy address bit 3 for a detailed explanation of this bit?s operation, see section 5.5, ?status interface? . ro ? p3td? 16.8 phy address bit 2 for a detailed explanation of this bit?s operation, see section 5.5, ?status interface? . ro ? p2li? 16.7 phy address bit 1 for a detailed explanation of this bit?s operation, see section 5.5, ?status interface? . ro ? p1cl? ? 16.6 phy address bit 0 for a detailed explanation of this bit?s operation, see section 5.5, ?status interface? . ro ? p0ac? 16.5 stream cipher test mode normal operation test mode rw ? 0 16.4 ics reserved read unspecified read unspecified rw/0 ? ? 16.3 nrz/nrzi encoding nrz encoding nrzi encoding rw ? 1 8 16.2 transmit invalid codes disabled enabled rw ? 0 16.1 ics reserved read unspecified read unspecified rw/0 ? 0 16.0 stream cipher disable stream cipher enabled stream cipher disabled rw ? 0
ics1893cf, rev. f, 03/01/07 mar. 2007 70 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.11.1 command override write enable (bit 16.15) the command override write enable bit provides an sta the abilit y to alter the co mmand override write (cw) bits located throughout the mii register set. a tw o-step process is required to alter the value of a cw bit: 1. step one is to issue a command override write, (that is, set bit 16.15 to logic one). this step enables the next mdio write to have the ability to alter any cw bit. 2. step two is to write to the register that includes the cw bit which requires modification. note: the command override write enable bit is a self-cle aring bit that is automatically reset to logic zero after the next mii write, thereby allowing onl y one subsequent write to alter the cw bits in a single register. to alter additional cw bits, the command override write enable bit must once again be set to logic one. 7.11.2 ics reserved (bits 16.14:11) idt is reserving these bits for future use. functionally, these bi ts are equivalent to ieee reserved bits. when one of these reserved bits is: ? read by an sta, the ics1893cf returns a logic zero. ? written to by an sta, the sta must use the default value specified in this data sheet. idt uses some reserved bits to invoke auxiliary func tions. to ensure proper op eration of the ics1893cf, an sta must maintain the default value of these bits . therefore, idt recommends that an sta always write the default value of any reserved bits during all management register write operations. 7.11.3 phy address (bits 16.10:6) these five bits hold the serial management port ad dress of the ics1893cf. during either a hardware reset or a power-on reset, the phy address is read from the led interface. (for information on the led interface, see section 5.5, ?status interface? and section 8.2.2, ?multi-functi on (multiplexed) pins: phy address and led pins? ). the phy address is then latched into this register. (the value of each of the phy address bits is unaffected by a software reset.) 7.11.4 stream cipher scrambler test mode (bit 16.5) the stream cipher scrambler test mode bit is used to force the ics1893cf to lose lock, thereby requiring the stream cipher scrambler to resynchronize. 7.11.5 ics reserved (bit 16.4) see section 7.11.2, ?ics reserved (bits 16.14:11)? , the text for which also applies here. 7.11.6 nrz/nrzi encoding (bit 16.3) this bit allows an sta to control wh ether nrz (not return to zero) or nrz i (not return to zero, invert on one) encoding is applied to the serial transmit data stream in 100base-tx mode. when this bit is logic: ? zero, the ics1893cf encodes the serial transmit data stream using nrz encoding. ? one, the ics1893cf encodes the serial tr ansmit data stream using nrzi encoding.
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 71 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.11.7 invalid error code test (bit 16.2) the invalid error code test bit allows an sta to force the ics1893cf to transmit symbols that are typically classified as invalid. the purpose of this test bit is to permit thorough testing of the 4b/5b encoding and the serial transmit data stream by allowing generation of bi t patterns that are considered invalid by the iso/iec 4b/5b definition. when this bit is logic: ? zero, the iso/iec defined 4b/5b translation takes place. ? one ? and the txer signal is asserted by the mac ? the mii input nibbles are translated according to table 7-17 . 7.11.8 ics reserved (bit 16.1) see section 7.11.2, ?ics reserved (bits 16.14:11)? , the text for which also applies here. 7.11.9 stream cipher disable (bit 16.0) the stream cipher disable bit allows an sta to control whether the ics189 3cf employs the stream cipher scrambler in the transmit and receive data paths. when this bit is set to logic: ? zero, the stream cipher encoder and decoder are both enabled for normal operations. ? one, the stream cipher encoder and decoder are disabled. this action results in an unscrambled data stream (for example, the ics1893cf transmits unscrambled idles, and so forth. note: the stream cipher scrambler can be used only for 100-mhz operations. table 7-17. invalid error code translation table symbol meaning mii input nibble translation v invalid code 0000 00000 v invalid code 0001 00001 v invalid code 0010 00010 v invalid code 0011 00011 h error 0100 00100 v invalid code 0101 00101 v invalid code 0110 00110 r esd 0111 00111 v invalid code 1000 00000 t esd 1001 01101 v invalid code 1010 01100 k ssd 1011 10001 v invalid code 1100 10000 v (s) invalid code 1101 11001 j ssd 1110 11000 i idle 1111 11111
ics1893cf, rev. f, 03/01/07 mar. 2007 72 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.12 register 17: quick poll detailed status register table 7-18 lists the bits for the quick-poll detailed status register. this register is a 16-bit read-only register used to provide an sta with detailed status of the ics1893cf operations. during reset, it is initialized to pre-defined default values. note: 1. for an explanation of acronyms used in table 7-18 , see chapter 1, ?abbreviations and acronyms? . 2. most of this register?s bits are latching high or latching low, which allows the ics1893cf to capture and save the occurrence of an event for an sta to read. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) 3. although some of these status bits are redund ant with other management registers, the ics1893cf provides this group of bits to minimize the number of serial management cycles required to collect the status data. table 7-18. quick poll detailed status register (register 17 [0x11]) bit definition when bit = 0 when bit = 1 ac- cess sf de- fault hex 17.15 data rate 10 mbps 100 mbps ro ? ? ? 17.14 duplex half duplex full duplex ro ? ? 17.13 auto-negotiation progress monitor bit 2 reference decode table reference decode table ro lmx 0 17.12 auto-negotiation progress monitor bit 1 reference decode table reference decode table ro lmx 0 17.11 auto-negotiation progress monitor bit 0 reference decode table reference decode table ro lmx 0 0 17.10 100base-tx signal lost valid signal signal lost ro lh 0 17.9 100basepll lock error pll locked pll failed to lock ro lh 0 17.8 false carrier detect normal ca rrier or idle false carrier ro lh 0 17.7 invalid symbol detected valid symbols observed inva lid symbol received ro lh 0 0 17.6 halt symbol detected no halt symbol received halt symbol received ro lh 0 17.5 premature end detected normal data stream stream contained two idle symbols ro lh 0 17.4 auto-negotiation complete auto-negotiation in process auto-negotiation complete ro ? 0 17.3 100base-tx signal detect signal present no signal present ro ? 0 0 17.2 jabber detect no jabber detected jabber detected ro lh 0 17.1 remote fault no remo te fault detected remote fault detected ro lh 0 17.0 link status link is not valid link is valid ro ll 0
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 73 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.12.1 data rate (bit 17.15) the data rate bit indicates the ?selec ted technology?. if the ics1893cf is in: ? hardware mode, the value of this bit is determined by the 10/100sel input pin. ? software mode, the value of this bit is determined by the data rate bit 0.13. when bit 17.15 is logic: ? zero, it indicates that 10-mhz operations are selected. ? one, the ics1893cf is indicating th at 100-mhz operations are selected. note: this bit does not imply any link status. 7.12.2 duplex (bit 17.14) the duplex bit indicates the ?selected technology?. if the ics1893cf is in: ? hardware mode, the value of this bit is determined by the dpxsel input pin. ? software mode, the value of this bit is determined by the duplex mode bit 0.8. when bit 17.14 is logic: ? zero, it indicates that half-duplex operations are selected. ? one, the ics1893cf is indicating that full-duplex operations are selected. note: this bit does not imply any link status. 7.12.3 auto-negotiation progress monitor (bits 17.13:11) the auto-negotiation progress monitor consists of th e auto-negotiation complete bit (bit 17.4) and the three auto-negotiation monitor bits (bits 17.13:11) . the auto-negotiation progress monitor continually examines the state of the auto-negotiation proc ess state machine and reports the status of auto-negotiation using the three auto-negotiation monito r bits. therefore, the value of these three bits provides the status of the auto-negotiation process. these three bits are initialized to lo gic zero in one of the following ways: ? a reset (see section 4.1, ?reset operations? ) ? disabling auto-neg otiation [see section 7.2.4, ?auto-negotiation enable (bit 0.12)? ] ? restarting auto-negotiation [see section 7.2.7, ?restart auto-negotiation (bit 0.9)? ] if auto-negotiation is enabled, these bits continually la tch the highest state that the auto-negotiation state machine achieves. that is, they are updated only if the binary value of the next state is greater than the binary value of the present state as outlined in table 7-19 .
ics1893cf, rev. f, 03/01/07 mar. 2007 74 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. note: an mdio read of these bits provides a history of the greatest progress achieved by the auto-negotiation process. in addition, the mdio read latches the present state of the auto-negotiation state machine for a subsequent read. 7.12.4 100base-tx receive signal lost (bit 17.10) the 100base-tx receive signal lost bit indicates to an sta whether the ics1893cf has lost its 100base-tx receive signal. if this bit is set to a logic: ? zero, it indicates the receive signal has remained valid since either the last read or reset of this register. ? one, it indicates the receive signal was lost since either the last read or reset of this register. this bit is a latching high bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) note: this bit has no definition in 10base-t mode. 7.12.5 100base pll lock error (bit 17.9) the phase-locked loop (pll) lock error bit indicates to an sta whether the ics1893cf has ever experienced a pll lock error. a pll lock error occurs when the pll fails to lock onto the incoming 100base data stream. if this bit is set to a logic: ? zero, it indicates that a pll lock error has not occurred since either the last read or reset of this register. ? one, it indicates that a pll lock error has occurred sinc e either the last read or reset of this register. this bit is a latching high bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) note: this bit has no definition in 10base-t mode. table 7-19. auto-negotiation state machine (progress monitor) auto-negotiation state machine auto-negotiation progress monitor auto- negotiation complete bit (bit 17.4) auto- negotiation monitor bit 2 (bit 17.13) auto- negotiation monitor bit 1 (bit 17.12) auto- negotiation monitor bit 0 (bit 17.11) idle 0000 parallel detected 0001 parallel detection failure 0010 ability matched 0011 acknowledge match failure 0100 acknowledge matched 0101 consistency match failure 0110 consistency matched 0111 auto-negotiation completed successfully 1000
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 75 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.12.6 false carrier (bit 17.8) the false carrier bit indicates to an sta the detecti on of a false carrier by the ics1893cf in 100base mode. a false carrier occurs when the ics1893cf begins evaluating potential data on the incoming 100base data stream, only to learn that it was not a valid /j/k/. if this bit is set to a logic: ? zero, it indicates a false carrier has not been detected since either the last read or reset of this register. ? one, it indicates a false carrier was detected since either the last read or reset of this register. this bit is a latching high bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) note: this bit has no definition in 10base-t mode. 7.12.7 invalid symbol (bit 17.7) the invalid symbol bit indicates to an sta the detection of an invalid symbol in a 100base data stream by the ics1893cf. when the ics1893cf is receiving a packet, it examines each received symbol to ensure the data is error free. if an error occurs, the port indicates this condi tion to the mac by asserting the rxer signal. in addition, the ics1893cf sets its invalid symbol bit to logic one. therefore, if th is bit is set to a logic: ? zero, it indicates an invalid symbol has not been de tected since either the last read or reset of this register. ? one, it indicates an invalid symbol was detected since either the last read or reset of this register. this bit is a latching high bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) note: this bit has no definition in 10base-t mode. 7.12.8 halt symbol (bit 17.6) the halt symbol bit indicates to an sta the detection of a halt symbol in a 100base data stream by the ics1893cf. during reception of a valid packet, the ics1893cf exam ines each symbol to ensure that the data being passed to the mac interface is error fr ee. in addition, it looks for specia l symbols such as the halt symbol. if a halt symbol is encountered, the ics189 3cf indicates this co ndition to the mac. if this bit is set to a logic: ? zero, it indicates a halt sy mbol has not been detected since either th e last read or reset of this register. ? one, it indicates a halt symbol was detected in the packet since either the last read or reset of this register. this bit is a latching high bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) note: this bit has no definition in 10base-t mode.
ics1893cf, rev. f, 03/01/07 mar. 2007 76 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.12.9 premature end (bit 17.5) the premature end bit indicates to an sta the detection of two consecutive idles in a 100base data stream by the ics1893cf. during reception of a valid packet, the ics1893cf exam ines each symbol to ensure that the data being passed to the mac interface is error free. if two co nsecutive idles are encountered, it indicates this condition to the mac by setting this bit. if this bit is set to a logic: ? zero, it indicates a premature end condition has not been detected since either the last read or reset of this register. ? one, it indicates a premature end condition was detected in the packet since either the last read or reset of this register. this bit is a latching high bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) note: this bit has no definition in 10base-t mode. 7.12.10 auto-negotiation complete (bit 17.4) the auto-negotiation comple te bit is used to indicate to an sta the completion of the auto-negotiation process. when this bit is set to logic: ? zero, it indicates that the auto-negotiation process is either not complete or is disabled by the control register?s auto-negotiation enable bit (bit 0.12) ? one, it indicates that the ics1893 cf has completed the auto-negotiation process and that the contents of management registers 4, 5, and 6 are valid. 7.12.11 100base-tx signal detect (bit 17.3) the 100base-tx signal detect bit indicates either the presence or absence of a si gnal on the twisted-pair receive pins (tp_rxp and tp_rxn) in 100base-tx mode. this bit is logic: ? zero when no signal is detected on the twisted-pair receive pins. ? one when a signal is present on the twisted-pair receive pins. 7.12.12 jabber detect (bit 17.2) bit 17.2 is functionally identical to bit 1.1. the ja bber detect bit indicates whether a jabber condition has occurred. this bit is a 10base-t function. 7.12.13 remote fault (bit 17.1) bit 17.1 is functionally identical to bit 1.4. 7.12.14 link status (bit 17.0) bit 17.0 is functionally identical to bit 1.2.
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 77 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.13 register 18: 10base -t operations register the 10base-t operations register provides an sta with the ability to monitor and control the ics1893cf activity while the ics1893cf is operating in 10base-t mode. note: 1. for an explanation of acronyms used in table 7-20 , see chapter 1, ?abbreviations and acronyms? . 2. during any write operation to any bit in this register, the sta must write the default value to all reserved bits. 7.13.1 remote jabber detect (bit 18.15) the remote jabber detect bit is provided to indicate that an ics1893cf port has detected a jabber condition on its receive path. this bit is reset to logic zero on a read of the 10base-t operations register. when this bit is logic: ? zero, it indicates a jabber condition has not occurred on the port?s receive path since either the last read of this register or the last reset of the associated port. ? one, it indicates a jabber condition has occurred on th e port?s receive path since either the last read of this register or the last re set of the associated port. this bit is a latching high bit. (for more information on latching high and latching low bits, see section 7.1.4.1, ?latching high bits? and section 7.1.4.2, ?latching low bits? .) note: this bit is provided for information purposes only (that is, no actions are taken by the port). the iso/iec specification defines the jabber condition in te rms of a port?s transmit path. to set this bit, an ics1893cf port monitors its receive path and applies the iso/iec jabber criteria to its receive path. table 7-20. 10base-t operations register (register 18 [0x12]) bit definition when bit = 0 when bit = 1 ac- cess sf de- fault hex 18.15 remote jabber detect no remote jabber condition detected remote jabber condition detected ro lh 0 ? 18.14 polarity reversed normal po larity polarity reversed ro lh 0 18.13 ics reserved read unspecified read unspecified rw/0 ? ? 18.12 ics reserved read unspecified read unspecified rw/0 ? ? 18.11 ics reserved read unspecified read unspecified rw/0 ? ? ? 18.10 ics reserved read unspecified read unspecified rw/0 ? ? 18.9 ics reserved read unspecified read unspecified rw/0 ? ? 18.8 ics reserved read unspecified read unspecified rw/0 ? ? 18.7 ics reserved read unspecified read unspecified rw/0 ? ? ? 18.6 ics reserved read unspecified read unspecified rw/0 ? ? 18.5 jabber inhibit normal jabber behavior jabber check disabled rw ? 0 18.4 ics reserved read unspecified read unspecified rw/1 ? 1 18.3 auto polarity inhibit polarity automatically corrected polarity not automatically corrected rw ? 0 0 18.2 sqe test inhibit normal sqe test behavior sqe test disabled rw ? 0 18.1 link loss inhibit normal link loss behavior link always = link pass rw ? 0 18.0 squelch inhibit normal squelch behavior no squelch rw ? 0
ics1893cf, rev. f, 03/01/07 mar. 2007 78 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.13.2 polarity reversed (bit 18.14) the polarity reversed bit is used to inform an sta whether the ics189 3cf has detected that the signals on the twisted-pair receive pins (tp_rxp and tp _rxn) are reversed. when the signal polarity is: ? correct, the ics1893cf sets bit 18.14 to a logic zero. ? reversed, the ics1893cf sets bit 18.14 to logic one. note: the ics1893cf can detect this situation and perf orm all its operations normally, independent of the reversal. 7.13.3 ics reserved (bits 18.13:6) see section 7.11.2, ?ics reserved (bits 16.14:11)? , the text for which also applies here. 7.13.4 jabber inhibit (bit 18.5) the jabber inhibit bit allows an sta to disable jabber detection. when an sta sets this bit to: ? zero, the ics1893cf enables 10base-t jabber checking. ? one, the ics1893cf disables its check for a jabber condition during data transmission. 7.13.5 ics reserved (bit 18.4) see section 7.11.2, ?ics reserved (bits 16.14:11)? , the text for which also applies here. 7.13.6 auto polarity inhibit (bit 18.3) the auto polarity inhibit bit allows an sta to prevent the automatic correcti on of a polarity reversal on the twisted-pair receive pins (tp_rxp and tp _rxn). if an sta sets this bit to logic: ? zero (the default), the ics1893cf automatically correc ts a polarity reversal on the twisted-pair receive pins. ? one, the ics1893cf either disables or inhibits th e automatic correction of reversed twisted-pair receive pins. note: the ics1893cf will not complete the auto-mdix function for an inverted polarity cable. this is a rare event with modern manufactured cables. full auto-negotiation and auto polarity correction will complete when the auto-mdix fu nction is disabled. software control for the auto-mdix function is available in mdio register 19 bits 9:8. 7.13.7 sqe test inhibit (bit 18.2) the sqe test inhibit bit allows an sta to prevent the generation of the signal qua lity error pulse. when an sta sets this bit to logic: ? zero, the ics1893cf enables its sqe test generation. ? one, the ics1893cf disables its sqe test generation. the sqe test provides the ability to verify that the co llision logic is active and functional. a 10base-t sqe test is performed by pulsing the collision signal for a short time after each packet transmission completes, that is, after txen goes inactive. note: 1. the sqe test is automatically in hibited in full-duplex and repeater modes, thereby disabling the functionality of this bit. 2. this bit is a control bit and not a status bit. ther efore, it is not updated to indicate this automatic inhibiting of the sqe test in full-duplex mode or repeater mode.
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 79 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.13.8 link loss inhibit (bit 18.1) the link loss inhibit bit allows an sta to preven t the ics1893cf from dropping the link in 10base-t mode. when an sta sets this bit to logic: ? zero, the state machine behaves normally and the link status is based on the signaling detected twisted- pair receiver inputs. ? one, the ics1893cf 10base-t link integrity test st ate machine is forced into the ?link passed? state regardless of the twisted-pair receiver input conditions. 7.13.9 squelch inhibit (bit 18.0) the squelch inhibit bit allows an sta to control th e ics1893cf squelch detection in 10base-t mode. when an sta sets this bit to logic: ? zero, before the ics1893cf can establish a valid link, the ics1893cf must receive valid 10base-t data. ? one, before the ics1893cf can establish a valid link, the ics1893cf must receive both valid 10base-t data followed by an idl.
ics1893cf, rev. f, 03/01/07 mar. 2007 80 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.14 register 19: extende d control register 2 the extended control register provides more refi ned control of the internal ics1893cf operations. note: 1. for an explanation of acronyms used in table 7-20 , see chapter 1, ?abbreviations and acronyms? . 2. during any write operation to any bit in this register, the sta must write the default value to all reserved bits. ? the default is the state of this pin at reset. table 7-21. extended control register (register [0x13]) bit definition when bit = 0 when bit = 1 ac- cess sf de- fault hex 19.15 node mode node mode repeater mode ro ? 0 4 19.14 hardware/software mode hardware mode software mode ro ? 1 19.13 remote fault no faults detected remote fault detected ro ? 0 19.12 ics reserved read unspecified read unspecified rw ? 0 19.11 ics reserved read unspecified read unspecified rw ? 0 2 19.10 ics reserved read unspecified read unspecified ro ? 0 19.9 amdix_en see table 7-22 see table 7-22 rw ? 1 19.8 mdi_mode see table 7-22 see table 7-22 rw ? 0 19.7 twisted pair tri-state enable, tptri twisted pair signals are not tri-stated or no effect twisted pair signals are tri-stated rw ? 0 0 19.6 ics reserved read unspecified read unspecified rw ? 0 19.5 ics reserved read unspecified read unspecified rw ? 0 19.4 ics reserved read unspecified read unspecified rw ? 0 19.3 ics reserved read unspecified read unspecified rw ? 0 1 19.2 ics reserved read unspecified read unspecified rw ? 0 19.1 ics reserved read unspecified read unspecified rw ? 0 19.0 automatic 100base-tx power down do not automatically power down power down automatically rw ? 1
chapter 7 management register set ics1893cf, rev. f, 03/01/07 mar. 2007 81 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 7.14.1 node configuration (bit 19.15) the node configuration bit indicates the nod/mode. ? in node mode: ? the sqe test default setting is enabled. ? the carrier sense signal (crs) is asserted in re sponse to either transmit or receive activity. ? the ics1893cf will only operate in the no de configuration. 7.14.2 hardware/software priority status (bit 19.14) the hardware/software priority st atus bit indicates the sw mode. ? the (mdio) register bits cont rol the ics1893cf configuration. ? the ics1893cf will only operate in the software configuration. 7.14.3 remote fault (bit 19.13) the iso/iec specification defines bit 5.13 as the remote fault bit, and bit 19.13 is functionally identical to bit 5.13. the remote fault bit is set based on the link control word received from the remote link partner. when this bit is a logic: ? zero, it indicates the remote link partner does not detect a link fault. ? one, it indicates to an sta that the remote link partner detects a link fault. 7.14.4 ics reserved (bits 19.12:10) see section 7.11.2, ?ics reserved (bits 16.14:11)? , the text for which also applies here. 7.14.5 auto-mdi/mdix (bits 19. 9:8) (new) the ics1893cf includes the auto-mdi/mdix crossover feature. the auto-mdi/mdi x feature automatically selects the correct mdi or mdix configuration to matc h the cable plant by automa tically swapping transmit and receive signal pairs at the phy. auto-mdi/mdix is defaulted on but ma y be disabled for test purposes using either the amdix_en (pin 10) or by writing (bits 19. 9:8). see table 7-22 for amdix_en (19,9) and mdi_mode (19,8) operation. when amdix_en (bit 19,9) is set to 0, the twisted pair transmit/receive is forced by the mdi_mode bit (19,8). note: holding (pin 10) amdix_en low will also disabl e the auto_mdix function and force pins tp_ap and tp_an to be the transmit pair and tp_bp and tp_bn to be the receive pair. amdix_en has a built in 50k ohm internal pull-up. table 7-22. amdix_en (pin 10) and control bits 19. 9:8 amdix_en (pin 10) amdix_en [reg 19:9] mdi_mode [reg 19:8] tx/rx mdi configuration x00straight x01cross 01xstraight
ics1893cf, rev. f, 03/01/07 mar. 2007 82 chapter 7 management register set ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. definitions: straight transmit = tp_ap & tp_an receive = tp_bp & tp_bn cross transmit = tp_bp & tp_bn receive = tp_ap & tp_an amdix_en (pin 10)amdix enable pin with 50 kohm pull-up resistor amdix_en [19:9] mdio register 13h bit 9 mdi_mode [19:8] mdio register 13h bit 8 7.14.6 twisted pair tri-state enable, tptri (bit 19.7) the ics1893cf provides a twisted pair tri- state enable bit. this bit forces the tp_txp and tp_txn signals to a high-impedance state. when this bit is set to logic: ? zero, the twisted pair interface is operational. ? one, the twisted pair interface is tri-stated. 7.14.7 ics reserved (bits 19.6:1) see section 7.11.2, ?ics reserved (bits 16.14:11)? , the text for which also applies here. 7.14.8 automatic 100base-tx power-down (bit 19.0) the automatic 100base-tx power down bit provides an sta with the means of enabling the ics1893cf to automatically shut down 100base-tx support f unctions when 10base-t operations are being used. when this bit is set to logic: ? zero, the 100base-tx transceiver does not pow er down automatically in 100base-tx mode. ? one, and the ics1893cf is operating in 10base-t mode, the 100base-tx transceiver automatically turns off to reduce the overall power consumption of the ics1893cf. note: there are other means of powering down the 100b ase-tx transceiver (for example, when the entire device is isol ated using bit 0:10). 1 1 x straight / cross (auto selected) default values: 1 1 0 straight / cross (auto selected) table 7-22. amdix_en (pin 10) and control bits 19. 9:8 amdix_en (pin 10) amdix_en [reg 19:9] mdi_mode [reg 19:8] tx/rx mdi configuration
chapter 8 pin diagram, listings, and descriptions ics1893cf, rev. f, 03/01/07 mar. 2007 83 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. chapter 8 pin diagram, li stings, and descriptions 8.1 ics1893cf pin diagram 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 vdd ref_in ref_out vdd crs col txd3 txd2 txd1 txd0 txen txclk vss rxer rxclk vdd poac vss p1cl p2li vss p3td vdd p4rd 10/100 amdix_en vss tp_ap tp_an vdd tp_bn tp_bp 17 18 19 20 21 22 23 24 vss vdd 10tcsr 100tcsr vss vdd reset_n vdd rxdv rxd0 rxd1 rxd2 rxd3 mdc mdio vss 32 31 30 29 28 27 26 25 48l ssop ics1893cf
ics1893cf, rev. f, 03/01/07 mar. 2007 84 chapter 8 pin diagram, listings, and descriptions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 8.2 ics1893cf pin descriptions table 8-1. ics1893cf mac interface pins signal name pin no. signal description mdio 26 management data input/output mdc 27 management data clock rxd3 28 receive data 3 rxd2 29 receive data 2 rxd1 30 receive data 1 rxd0 31 receive data 0 rxdv 32 receive data valid rxclk 34 receive clock rxer 35 receive error txclk 37 transmit clock txen 38 transmit enable txd0 39 transmit data 0 txd1 40 transmit data 1 txd2 41 transmit data 2 txd3 42 transmit data 3 col 43 collision detect crs 44 carrier sense table 8-2. ics 1893cf multifunction pi ns: phy address and led pins signal name pin no. signal description p4rd 8 bit 4 of phy address, phyad[4], or receive led p3td 6 bit 3 of phy address, phyad[3], or transmit led p2li 4 bit 2 of phy address, phyad[2], or link integrity led p1cl 3 bit 1 of phy address, phyad[1], or collision led p0ac 1 bit 0 of phy address, phyad[0], or activity led table 8-3. ics1893cf configuration pins signal name pin no. signal description 10/100 9 output indication, high=100basetx operation amdix_en 10 auto-mdix enable (built-in internal 50k ohm pull-up) 100tcsr 20 100m transmit current set resistors 10tcsr 19 10m transmit current set resistor
chapter 8 pin diagram, listings, and descriptions ics1893cf, rev. f, 03/01/07 mar. 2007 85 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 8.2.1 transformer interface pins transformer connections on the ics1893cf signals tp_ap, tp_an, tp_bp and tp_bn are shown in table 8.4. the previous tp_ct pin on the ics1893af is not used with the ics1893cf. the typical twisted pair transformers connections are shown in chapter 5. the transformer must be 1:1 ratio and symetrical for 10/100 mdi/mdix applications since the transmit twisted pair and receive twisted pair are interchangeable. ics1893 phys do not have power connections to the transformer. all transformer power is supplied by the ics1893. note the twisted pair ar e polarity sensitive and mu st connect to the rj45 with the same polarity as shown in the figure. table 8-4 lists the pins for the transformer interface group of pins. 8.2.2 multi-function (multiplexed) pins: phy address and led pins table 8-5 lists the pins for the multi-function group of pi ns (that is, the multiplexed phy address / led pins). note: 1. during either a power-on reset or a hardware rese t, each multi-function configuration pin is an input that is sampled when the ics1893cf exits the reset state. after sampling is complete, these pins are output pins that ca n drive status leds. 2. a software reset does not affect the state of a multi- function configuration pin. during a software reset, all multi-function configuration pins are outputs. 3. each multi-function configuration pin must be pulled either up or down with a resistor to establish the address of the ics1893cf. leds placed in series with these resistors provide a designated status indicator. caution: all pins listed in table 8-5 must not float. 4. as outputs, the asserted state of a multi-function configuration pin is the inverse of the sense sampled during reset. this inversion provides a signal that can illuminate an led during an asserted state. for example, if a multi-function configuration pin is pulled down to ground through an led and a current-limiting resistor, then the sampled sense of the input is lo w. to illuminate an led for the asserted state requires the output to be high. ref_in 47 frequency reference inpu t: 25 mhz input clock or crystal ref_out 46 frequency refere nce output for crystal resetn 23 system re set (active low) table 8-4. ics1893cf transformer interface pins signal name pin no. signal description tp_ap 12 twisted pair a positive tp_an 13 twisted pair a negative tp_bp 16 twisted pair b positive tp_bn 15 twisted pair b negative table 8-3. ics1893cf configuration pins signal name pin no. signal description
ics1893cf, rev. f, 03/01/07 mar. 2007 86 chapter 8 pin diagram, listings, and descriptions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. note: each of these pins monitor the data link by providing signals that directly drive leds. table 8-5. phy address and led pins pin name pin number pin type pin description p0ac 1 input or output phy (address bit) 0 / activity led. for more information on this pin, see section 5.5, ?status interface? . ? this multi-function configuration pin is: ? an input pin during either a power-on reset or a hardware reset. in this case, this pin configures the ics1893cf phy address bit 0. ? an output pin following reset. in this case, this pin provides indication of receive ?or? transmit activity. as an input pin: ? this pin establishes the address for the ics1893cf. when the signal on this pin is logic: ? low, that address bit is set to logic zero. ? high, that address bit is set to logic one. as an output pin: ? when the signal on this pin is: ? de-asserted, this state indicates the ics1893cf does not have activity. ? asserted, this state indicate s the ics1893cf has activity. caution: this pin must not float. (see the notes at section 8.2.2, ?multi-function (multiplexed) pins: phy address and led pins? .) p1cl 3 input or output phy (address bit) 1 / collision led. for more information on this pin, see section 5.5, ?status interface? . ? this multi-function configuration pin is: ? an input pin during either a power-on reset or a hardware reset. in this case, this pin configures the ics1893cf phy address bit 1. ? an output pin following reset. in th is case, this pin provides collision status for the ics1893cf. as an input pin: ? this pin establishes the address for the ics1893cf. when the signal on this pin is logic: ? low, that address bit is set to logic zero. ? high, that address is set to logic one. as an output pin: ? when the signal on this pin is: ? de-asserted, this state indicates the ics1893cf does not detect any collisions. ? asserted, this stat e indicates the ics1893cf detects collisions. ? the ics1893cf asserts its collision led for a period of approximately 70 msec when it detects a collision. caution: this pin must not float. (see the notes at section 8.2.2, ?multi-function (multiplexed) pins: phy address and led pins? .)
chapter 8 pin diagram, listings, and descriptions ics1893cf, rev. f, 03/01/07 mar. 2007 87 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. p2li 4 input or output phy (address bit) 2 / link integrity led. for more information on this pin, see section 5.5, ?status interface? . ? this multi-function configuration pin is: ? an input pin during either a power-on reset or a hardware reset. in this case, this pin configures the address of the ics1893cf phy address bit 2. ? an output pin following reset. in this case, this pin provides link status for the ics1893cf. as an input pin: ? this pins establishes the address for the ics1893cf. when the signal on this pin is logic: ? low, that address bit is set to logic zero. ? high, that address bit is set to logic one. as an output pin: ? when the signal on this pin is: ? de-asserted, this state indicates the ics1893cf does not have a link. ? asserted, this state indicate s the ics1893cf has a valid link. caution: this pin must not float. (see the notes at section 8.2.2, ?multi-function (multiplexed) pins: phy address and led pins? .) p3td 6 input or output phy (address bit) 3 / transmit data led. for more information on this pin, see section 5.5, ?status interface? . ? these multi-function configuration pins are: ? input pins during either a power-on reset or a hardware reset. in this case, these pins configure the address of the ics1893cf phy address bit 3. ? output pins following reset. in this case, this pin provides indication of transmit activity. as an input pin: ? this pin establishes the address for the ics1893cf. when the signal on one of these pins is logic: ? low, that address bit is set to logic zero. ? high, that address bit is set to logic one. as an output pin: ? when the signal on this pin is: ? de-asserted, this state indicates the ics1893cf does not have transmit activity. ? asserted, this state indicates t he ics1893cf has transmit activity. caution: this pin must not float. (see the notes at section 8.2.2, ?multi-function (multiplexed) pins: phy address and led pins? .) table 8-5. phy address and led pins pin name pin number pin type pin description
ics1893cf, rev. f, 03/01/07 mar. 2007 88 chapter 8 pin diagram, listings, and descriptions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. p4rd 8 input or output phy (address bit) 4 / receive data led. for more information on this pin, see section 5.5, ?status interface? . ? this multi-function configuration pin is: ? an input pin during either a power-on reset or a hardware reset. in this case, this pin configures t he ics1893cf when it is in either hardware mode or software mode. ? an output pin following reset. in th is case, this pin provides activity status of the ics1893. an an input pin: ? this pin establishes the address for the ics1893cf. when the signal on this pin is logic: ? low, that address bit is set to logic zero. ? high, that address bit is set to logic one. as an output pin: ? when the signal on this pin is: ? de-asserted, this state indicates the ics1893cf does not have receive activity. ? asserted, this state indicates t he ics1893cf has receive activity. caution: this pin must not float. (see the notes at section 8.2.2, ?multi-function (multiplexed) pins: phy address and led pins? .) table 8-5. phy address and led pins pin name pin number pin type pin description
chapter 8 pin diagram, listings, and descriptions ics1893cf, rev. f, 03/01/07 mar. 2007 89 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 8.2.3 configuration pins table 8-6 lists the configuration pins. table 8-6. configuration pins pin name pin number pin type pin description 10/100sel 9 output 10base-t / 100base-tx select. ? this pin acts as an output that indicates the current status of this pin. in this case, when the signal on this pin is logic: ? low, this pin indicates 10base-t operations are selected. ? high, this pin indicates 100base-tx operations are selected. 10tcsr 19 output 10m transmit current set resistor. ? a resistor, connected between this pin and ground, is required to establish the value of the transmit current used in 10base-t mode. ? the value and tolerance of this resistor is specified in section 9.3, ?recommended component values *? . 100tcsr 20 output 100m transmit current set resistor. ? a resistor, connected between this pin and ground, is required to establish the value of the transmit current used in 100base-tx mode. ? the value and tolerance of this resistor is specified in section 9.3, ?recommended component values *? . ref_in 47 input (frequency) reference input. this pin is connected to a 25-mhz oscillator. for a tolerance, see section 9.5.1, ?timing for clock reference in (ref_in) pin? . ref_out 46 output (frequency) reference output. this pin is used with a crystal. resetn 23 input (system) reset ( active low ). ? when the signal on this active-low pin is logic: ? low, the ics1893cf is in hardware reset. ? high, the ics1893cf is operational. ? for more information on hardware resets, see the following: ? section 4.1.2.1, ?hardware reset? ? section 9.5.16, ?reset: hard ware reset and power-down?
ics1893cf, rev. f, 03/01/07 mar. 2007 90 chapter 8 pin diagram, listings, and descriptions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 8.2.4 mac interface pins this section lists pin descriptions for each of the following interfaces ? section 8.2.4.1, ?mac interface pi ns for media independent interface? 8.2.4.1 mac interface pins for media independent interface table 8-7 lists the mac interface pin descriptions for the mii. table 8-7. mac interface pins: media i ndependent interface (mii) pin name pin number pin type pin description col 43 output collision (detect). the ics1893cf asserts a signal on the col pin when the ics1893cf detects receive activity while transmitti ng (that is, while the txen signal is asserted by the mac, that is, when transmitting). when the mode is: ? 10base-t, the ics1893cf detects receive activity by monitoring the un-squelched mdi receive signal. ? 100base-tx, the ics1893cf detects receive activity when there are two non-contiguous zeros in any 10-bit symbol derived from the mdi receive data stream. note: 1. the signal on the col pin is not synchronous to either rxclk or txclk. 2. in full-duplex mode, the col signal is disabled and always remains low. 3. the col signal is asserted as part of the signal quality error (sqe) test. this assertion can be suppressed with the sqe test inhibit bit (bit 18.2). crs 44 output carrier sense. when the ics1893cf mode is: ? half-duplex, the ics1893cf asserts a signal on its crs pin when it detects either receive or transmit activity. ? either full-duplex or repeater mode, the ics1893cf asserts a signal on its crs pin only in response to receive activity. note: the signal on the crs pin is not synchronous to the signal on either the rxclk or txclk pin. mdc 27 input management data clock. the ics1893cf uses the signal on the mdc pin to synchronize the transfer of management information between the ics1893cf and the station management entity (sta), us ing the serial mdio data line. the mdc signal is sourced by the sta.
chapter 8 pin diagram, listings, and descriptions ics1893cf, rev. f, 03/01/07 mar. 2007 91 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. mdio 26 input/ output management data input/output. the signal on this pin can be tri-stated and can be driven by one of the following: ? a station management entity (sta), to transfer command and data information to the registers of the ics1893cf. ? the ics1893cf, to transfer status information. all transfers and sampling are synchronous with the signal on the mdc pin. note: if the ics1893cf is to be used in an application that uses the mechanical mii specification, mdio must have a 1.5 k ? 5% pull-up resistor at the ics1893cf end and a 2 k ? 5% pull-down resistor at the station management end. (these resistors enable the station management to determine if the connection is intact.) rxclk 34 output receive clock. the ics1893cf sources the rxclk to the mac interface. the ics1893cf uses rxclk to synchronize the signals on the following pins: rxd[3:0], rxdv, and rxer. the following table contrasts the behavior on the rxclk pin when the mode for the ics1893cf is either 10base-t or 100base-tx. note: the signal on the rxclk pin is conditioned by the rxtri pin. table 8-7. mac interface pins: media i ndependent interface (mii) ( continued ) pin name pin number pin type pin description 10base-t 100base-tx the rxclk frequency is 2.5 mhz. the rxclk frequency is 25 mhz. the ics1893cf generates its rxclk from the mdi data stream using a digital pll. when the mdi data stream terminates, the pll continues to operate, synchronously referenced to the last packet received. the ics1893cf generates its rxclk from the mdi data stream while there is a valid link (that is, either data or idles). in the absence of a link, the ics1893cf uses the ref_in clock to generate the rxclk. the ics1893cf switches between clock sources during the period between when its crs is asserted and prior to its rxdv being asserted. while the ics1893cf is locking onto the incoming data stream, a clock phase change of up to 360 degrees can occur. while the ics1893cf is bringing up a link, a clock phase change of up to 360 degrees can occur. the rxclk aligns once per packet. the rxclk aligns once, when the link is being established.
ics1893cf, rev. f, 03/01/07 mar. 2007 92 chapter 8 pin diagram, listings, and descriptions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. rxd0 rxd1 rxd2 rxd3 31 30 29 28 output receive data 0?3. ? rxd0 is the least-significant bit and rxd3 is the most-significant bit of the mii receive data nibble. ? while the ics1893cf asserts rxdv, the ics1893cf transfers the receive data signals on the rxd0?r xd3 pins to the mac interface synchronously on the rising edges of rxclk. rxdv 32 output receive data valid. the ics1893cf asserts rxdv to indicate to the mac that data is available on the mii receive bus (rxd[3:0]). the ics1893cf: ? asserts rxdv after it detects and recovers the start-of-stream delimiter, /j/k/. (for the timing reference, see chapter 9.5.6, ?100m/mii media independent interface: synchronous receive timing? .) ? de-asserts rxdv after it detects either the end-of-stream delimiter (/t/r/) or a signal error. note: rxdv is synchronous with the receive data clock, rxclk. rxer 35 output receive error. when the mac interface is in: ? 10m mii mode, rxer is not used. ? 100m mii mode, the ics1893cf asserts a signal on the rxer pin when either of the following two conditions are true: ? errors are detected during the reception of valid frames ? a false carrier is detected note: 1. an ics1893cf asserts a signal on the rxer pin upon detection of a false carrier so that repeater applications can prevent the propagation of a false carrier. 2. the rxer signal always transitions synchronously with rxclk. 3. the signal on rxer pin is conditioned by the rxtri pin. txclk 37 output transmit clock. the ics1893cf generates this clock si gnal to synchronize the transfer of data from the mac interface to the ics1893cf. when the mode is: ? 10base-t, the txclk frequency is 2.5 mhz. ? 100base-tx, the txclk frequency is 25 mhz. table 8-7. mac interface pins: media i ndependent interface (mii) ( continued ) pin name pin number pin type pin description
chapter 8 pin diagram, listings, and descriptions ics1893cf, rev. f, 03/01/07 mar. 2007 93 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. txd0 txd1 txd2 txd3 39 40 41 42 input transmit data 0?3. ? txd0 is the least-significant bit and txd3 is the most-significant bit of the mii transmit data nibble received from the mac. ? the ics1893cf samples its txen signal to determine when data is available for transmission. when txen is asserted, the signals on a the txd[3:0] pins are sampled synchronously on the rising edges of the txclk signal. txen 38 input transmit enable. in mii mode: ? the ics1893cf samples its txen signal to determine when data is available for transmission. when txen is asserted, the ics1893cf begins sampling the data nibbles on the transmit data lines txd[3:0] synchronously with txclk. the ics 1893cf then transmits this data over the media. ? following the de-assertion of txen, the ics1893cf terminates transmission of nibbles over the media. table 8-7. mac interface pins: media i ndependent interface (mii) ( continued ) pin name pin number pin type pin description
ics1893cf, rev. f, 03/01/07 mar. 2007 94 chapter 8 pin diagram, listings, and descriptions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 8.2.5 ground and power pins table 8-8. ground and power pins signal name pin no. signal description power vdd 7 3.3v vdd 14 3.3v vdd 18 3.3v vdd 22 3.3v vdd 24 3.3v vdd 33 3.3v vdd 45 3.3v vdd 48 3.3v ground vss 2 vss 5 vss 11 vss 17 vss 21 vss 25 vss 36
chapter 8 pin diagram, listings, and descriptions ics1893cf, rev. f, 03/01/07 mar. 2007 95 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 8.3 ics1893ck pin diagram with mdix pinout (56l, 8x8 mlf2) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 28 27 26 25 24 23 22 21 20 19 18 17 16 15 42 41 40 39 38 37 36 35 34 33 32 31 30 29 56 55 54 53 52 51 50 49 48 47 46 45 44 43 p4rd vdd p3td vss p2li p1cl vss p0ac vdd ref_in ref_out vdd crs col txd3 txd2 txd1 txd0 txen txclk vss rxer rxclk vdd rxdv rxd0 rxd1 rxd2 mdc mdio vss vss vdd vss vss vss vss vss reset_n vss vdd 10/100 amdix_en vss tp_ap tp_an vdd vdd tp_bn tp_bp vss vdd 10tcsr 100tcsr vss ics1893ck 8x8 56l mlf2 rxd3
ics1893cf, rev. f, 03/01/07 mar. 2007 96 chapter 8 pin diagram, listings, and descriptions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 8.3.1 ics1893ck pin descriptions the ics1893ck pin signal descriptions are identica l in function to the ics1893cf except for the pin numbers. see section 8.1 for descriptions. table 8-9. ics1893ck mac interface pins signal name pin no. description mdio 26 management data input/output mdc 27 management data clock rxd3 28 receive data 3 rxd2 29 receive data 2 rxd1 30 receive data 1 rxd0 31 receive data 0 rxdv 32 receive data valid rxclk 34 receive clock rxer 35 receive error txclk 37 transmit clock txen 38 transmit enable txd0 39 transmit data 0 txd1 40 transmit data 1 txd2 41 transmit data 2 txd3 42 transmit data 3 col 43 collision detect crs 44 carrier sense table 8-10. ics1893ck multifunction pins: phy address and led pins signal name pin no. signals description p4rd 56 phyad[4] / receive led p3td 54 phyad[3] / transmit led p2li 52 phyad[2] / link led p1cl 51 phyad[1] / collision led p0ac 49 phyad[0] / activity led table 8-11. ics1893ck configuration pins signal name pin no. signals description 10/100 1 output speed indication, high=100basetx amdix_en 2 auto-mdix enable (bu ilt-in internal 50k ohm pull-up) 10tcsr 12 10m transmit amplitude current set resistor 100tcsr 13 100m transmit amp litude current set resistor
chapter 8 pin diagram, listings, and descriptions ics1893cf, rev. f, 03/01/07 mar. 2007 97 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 8.3.2 transformer interface pins transformer connections on the ics1893ck signal s tp_ap, tp_an, tp_bp and tp_bn are shown in table 8-12. the previous tp_ct pin used on the ics1 893cf is not used with the ics1893ck. the typical twisted pair transformers connections are shown in chapter 5. the transformer must be 1:1 ratio and symetrical for 10/100 mdi/mdix applications since the transmit twisted pair and receive twisted pair are interchangeable. ics1893 phys do not have power connections to the transformer. all transformer power is supplied by the ics1893ck. note the twisted pairs are polarity sensitive and must connect to the rj45 with the same polarity as shown in the figure. pay particular attention to polarity of the the ?b? pair being reversed in pad sequence. ref_in 47 frequency ref input: 25mhz clock or crystal ref_out 46 frequency re f output for crystal resetn 17 system reset (active low) table 8-12. ics1893ck transformer interface pins signal name pin no. signals description tp_ap 4 twisted pair a positive tp_an 5 twisted pair a negative tp_bp 9 twisted pair b positive tp_bn 8 twisted pair b negative table 8-11. ics1893ck configuration pins signal name pin no. signals description
ics1893cf, rev. f, 03/01/07 mar. 2007 98 chapter 8 pin diagram, listings, and descriptions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 8.3.3 ground and power pins table 8-13. ics1893ck ground and power pins signal name pin no. signals description vdd 6 power 3.3v vdd 7 power 3.3v vdd 11 power 3.3v vdd 15 power 3.3v vdd 23 power 3.3v vdd 33 power 3.3v vdd 45 power 3.3v vdd 48 power 3.3v vdd 55 power 3.3v vss 3 ground vss 10 ground vss 14 ground vss 16 ground vss 18 ground vss 19 ground vss 20 ground vss 21 ground vss 22 ground vss 24 ground vss 25 ground vss 36 ground vss 50 ground vss 53 ground
chapter 9 dc and ac operating conditions ics1893cf, rev. f, 03/01/07 mar. 2007 99 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. chapter 9 dc and ac operating conditions 9.1 absolute maximum ratings table 9-1 lists absolute maximum ratings. stresses ab ove these ratings can permanently damage the ics1893cf. these ratings, which are standard values for idt commercially rated parts, are stress ratings only. functional operation of the ics1893cf at these or any other conditions above those indicated in the operational sections of the specifications is not implie d. exposure to absolute maximum rating conditions for extended periods can affect product reliability. elec trical parameters are guar anteed only over the range of the recommended operating temperature. 9.2 recommended operating conditions table 9-1. absolute maximum ratings for ics1893cf item rating vdd (measured to vss) -0.3 v to 3.6v digital inputs / outputs -0.3 v to vdd +0.3 v storage temperature -55 c to +150 c junction temperature 125 c soldering temperature 260 c power dissipation see section 9.4.1, ?dc operating ch aracteristics for supply current? table 9-2. recommended operating conditions for ics1893cf parameter symbols min. max. units ambient operating temperature - commercial t a 0+70 c ambient operating temp erature - industrial t a -40 +85 c power supply voltage (meas ured to vss) vdd +3.14 +3.47 v
ics1893cf, rev. f, 03/01/07 mar. 2007 100 chapter 9 dc and ac operating conditions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.3 recommended component values * ? there are two ieee std. 802.3 requ irements that define the tolerance for the frequency of the oscillator. ? clause 22.2.2.1 requires the mii tx_clk to have an accuracy of 100 ppm. ? clause 24.2.3.4 is more string ent. it requires the code-bit timer to have an accuracy of 0.005% (that is, 50 ppm). figure 9-1. ics1893cf 10tcsr and 100tcsr * for backward compatibillity, refer to the ?1893c alternate schem atic? application note. table 9-3. recommended component values for ics1893cf parameter minimum typical maximum tolerance units oscillator frequency ? 25 ? 50 ppm ? mhz 10tcsr resistor value ? 2.43k ? 1% ? 100tcsr resistor value ? see figure 9-1 ?1% ? led resistor value 510 1k 10k ? ? note: 1. the bias resistor networks set the 10bas et and 100basetx output amplitude levels. 2. amplitude is directly related to current sourced out of the 10tcsr and 100tcsr pins. 3. resistor values shown above are typical. user shou ld check amplitudes and adjust for transformer effects 4. the vdd connection to the 18.2k resistor can connect to any vdd. the 18.2k resistor provides negativ e feedback to compensate for vdd changes. lowering the 18.2k value will lower the 100baset amplitude . typical board layouts 10tcsr and 100tcsr bias resistors ics1893cf 18 19 20 vdd 10tcsr 100tcsr 2.43k ? 1% vdd 18.2k ? 1% 10tcsr 1.82k ? 1% 100tcsr
chapter 9 dc and ac operating conditions ics1893cf, rev. f, 03/01/07 mar. 2007 101 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.4 dc operating characteristics this section lists the ics1893cf dc operating characteristics. 9.4.1 dc operating characteristics for supply current table 9-4 lists the dc operating characteristics for the supply current to the ics1893cf under various conditions. note: all vdd_io measurements are taken wit h respect to vss (which equals 0 v). ? these supply current parameters are measured through vdd pins to the ics1893cf. the supply current parameters include external transformer currents. ? measurements taken with 100% data trans mission and the minimum inter-packet gap. 9.4.2 dc operating characteristics for ttl inputs and outputs table 9-5 lists the 3.3-v dc operating characteristic s of the ics1893cf ttl inputs and outputs. note: all vdd_io measurements are taken wit h respect to vss (which equals 0 v). table 9-4. dc operating characteristics for supply current parameter operating mode symbol min. typ. max. units supply current? 100base-tx? idd_io ? ? 11 ma idd ? ? 125 ma supply current? 10 base-t? idd_io ? ? 8 ma idd ? ? 160 ma supply current? auto-negotiation idd_io ? ? 8 ma idd ? ? 90 ma supply current? power-down idd_io ? ? 5 ma idd ? ? 5 ma supply current? reset idd ? ? 11 ma table 9-5. 3.3-v dc operating characteristics for ttl inputs and outputs parameter symbol conditions min. max. units ttl input high voltage v ih vdd_io = 3.47 v ? 2.0 ? v ttl input low voltage v il vdd_io = 3.47 v ? ? 0.8 v ttl output high voltage v oh vdd_io = 3.14 v i oh = ?4 ma 2.4 ? v ttl output low voltage v ol vdd_io = 3.14 v i ol = +4 ma ? 0.4 v ttl driving cmos, output high voltage v oh vdd_io = 3.14 v i oh = ?4 ma 2.4 ? v ttl driving cmos, output low voltage v ol vdd_io = 3.14 v i ol = +4 ma ? 0.4 v
ics1893cf, rev. f, 03/01/07 mar. 2007 102 chapter 9 dc and ac operating conditions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.4.3 dc operating characteristics for ref_in table 9-6 lists the 3.3-v dc characte ristics for the ref_in pin. note: the ref_in input switch point is 50% of vdd. 9.4.4 dc operating characteristics for media independent interface table 9-7 lists dc operating characteristics for the medi a independent interface (mii) for the ics1893cf. table 9-6. 3.3-v dc operating char acteristics for ref_in parameter symbol test conditions min. max. units input high voltage v ih vdd_io = 3.47 v 2.97 ? v input low voltage v il vdd_io = 3.14 v ? 0.33 v table 9-7. dc operating characteristics for media independent interface parameter conditions minimum typical maximum units mii input pin capacitance ? ? ? 8 pf mii output pin capacitance ? ? ? 14 pf mii output drive impedance vdd_io = 3.3v ? 60 ? ?
chapter 9 dc and ac operating conditions ics1893cf, rev. f, 03/01/07 mar. 2007 103 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5 timing diagrams 9.5.1 timing for clock reference in (ref_in) pin table 9-8 lists the significant time periods for signals on the clock reference in (ref_in) pin. figure 9-2 shows the timing diagram for the time periods. note: the ref_in switching point is 50% of vdd. figure 9-2. ref_in timing diagram table 9-8. ref_in timing time period parameter conditions min. typ. max. units t1 ref_in duty cycle ? 45 50 55 % t2 ref_in period ? ? 40 ? ns ref_in t1 t2
ics1893cf, rev. f, 03/01/07 mar. 2007 104 chapter 9 dc and ac operating conditions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.2 timing for transmit clock (txclk) pins table 9-9 lists the significant time periods for signals on the transmit clock (txclk) pins for the various interfaces. figure 9-3 shows the timing diagram for the time periods. figure 9-3. transmit clock timing diagram table 9-9. transmit clock timing time period parameter conditions min. typ. max. units t1 txclk duty cycle ? 35 50 65 % t2a txclk period 100m mii (100base-tx) ? 40 ? ns t2b txclk period 10m mii (10base-t) ? 400 ? ns t1 t2x txclk
chapter 9 dc and ac operating conditions ics1893cf, rev. f, 03/01/07 mar. 2007 105 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.3 timing for receive clock (rxclk) pins table 9-10 lists the significant time periods for signals on the receive clock (rxclk) pins for the various interfaces. figure 9-4 shows the timing diagram for the time periods. figure 9-4. receive clock timing diagram table 9-10. mii receive clock timing time period parameter conditions min. typ. max. units t1 rxclk duty cycle ? 35 50 65 % t2a rxclk period 100m mii (100base-tx) ? 40 ? ns t2b rxclk period 10m mii (10base-t) ? 400 ? ns rxclk t1 t2
ics1893cf, rev. f, 03/01/07 mar. 2007 106 chapter 9 dc and ac operating conditions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.4 100m mii: synchronous transmit timing table 9-11 lists the significant time periods for the 100m mii interface synchronous transmit timing. the time periods consist of timings of signals on the following pins: ? txclk ? txd[3:0] ? txen ? txer figure 9-5 shows the timing diagra m for the time periods. figure 9-5. 100m mii / 100m stream interface synchronous transmit timing diagram table 9-11. 100m mii / 100m stream interface: synchronous transmit timing time period parameter conditions min. typ. max. units t1 txd[3:0], txen, txer setup to txclk rise ? 15 ? ? ns t2 txd[3:0], txen, txer hold after txclk rise ? 0 ? ? ns t1 t2 txclk txd[3:0] txen txer
chapter 9 dc and ac operating conditions ics1893cf, rev. f, 03/01/07 mar. 2007 107 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.5 10m mii: synchronous transmit timing table 9-12 lists the significant time perio ds for the 10m mii synch ronous transmit timing. the time periods consist of timings of signals on the following pins: ? txclk ? txd[3:0] ? txen ? txer figure 9-6 shows the timing diagra m for the time periods. figure 9-6. 10m mii synchronous transmit timing diagram table 9-12. 10m mii: synchronous transmit timing time period parameter conditions min. typ. max. units t1 txd[3:0], txen, txer setup to txclk rise ? 375 ? ? ns t2 txd[3:0], txen, txer hold after txclk rise ? 0 ? ? ns t1 t2 txclk txd[3:0] txen txer
ics1893cf, rev. f, 03/01/07 mar. 2007 108 chapter 9 dc and ac operating conditions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.6 100m/mii media independent interface: synchronous receive timing table 9-13 lists the significant time periods for the mii / 100m stream interface synchronous receive timing. the time periods consist of timings of signals on the following pins: ? rxclk ? rxd[3:0] ? rxdv ? rxer figure 9-7 shows the timing diagra m for the time periods. figure 9-7. mii interface synchronous receive timing diagram table 9-13. mii interface: synchronous receive timing time period parameter min. typ. max. units t1 rxd[3:0], rxdv, and rxer setup to rxclk rise 10.0 ? ? ns t2 rxd[3:0], rxdv, and rxer hold after rxclk rise 10.0 ? ? ns t1 t2 rxclk rxd[3:0] rxdv rxer
chapter 9 dc and ac operating conditions ics1893cf, rev. f, 03/01/07 mar. 2007 109 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.7 mii management interface timing table 9-14 lists the significant time perio ds for the mii management interface timing (which consists of timings of signals on the mdc and mdio pins). figure 9-8 shows the timing diagram for the time periods. ? the ics1893cf is tested at 25 mhz (a 40-ns period) wi th a 50-pf load. designs must account for all board loading of mdc. figure 9-8. mii management interface timing diagram table 9-14. mii management interface timing time period parameter conditions min. typ. max. units t1 mdc minimum high time ? 160 ? ? ns t2 mdc minimum low time ? 160 ? ? ns t3 mdc period ? 400? ? ? ns t4 mdc rise time to mdio valid ? 0 ? 300 ns t5 mdio setup time to mdc ? 10 ? ? ns t6 mdio hold time after mdc ? 10 ? ? ns mdc mdio (output) mdc mdio (input) t1 t2 t3 t4 t5 t6
ics1893cf, rev. f, 03/01/07 mar. 2007 110 chapter 9 dc and ac operating conditions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.8 10m media independent interface: receive latency table 9-15 lists the significant time periods for the 10m mii timing. the time periods consist of timings of signals on the following pins: ? tp_rx (that is, the mii tp_rxp and tp_rxn pins) ? rxclk ? rxd figure 9-9 shows the timing diagra m for the time periods. figure 9-9. 10m mii receive latency timing diagram table 9-15. 10m mii receive latency time period parameter conditions min. typ. max. units t1 first bit of /5/ on tp_rx to /5/d/ on rxd 10m mii ? 6.5 7 bit times ? manchester encoding is not shown. 5 5 d 5 t1 tp_rx ? rxclk rxd
chapter 9 dc and ac operating conditions ics1893cf, rev. f, 03/01/07 mar. 2007 111 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.9 10m media independent interface: transmit latency table 9-16 lists the significant time perio ds for the 10m mii trans mit latency. the time periods consist of timings of signals on the following pins: ? txen ? txclk ? txd (that is, txd[3:0]) ? tp_tx (that is, tp_txp and tp_txn) figure 9-10 shows the timing diagram for the time periods. figure 9-10. 10m mii transmit latency timing diagram table 9-16. 10m mii transmit latency timing time period parameter conditions min. typ. max. units t1 txd sampled to mdi output of first bit 10m mii ? 1.2 2 bit times txclk txen txd ? manchester encoding is not shown. 55 5 t1 tp_tx ?
ics1893cf, rev. f, 03/01/07 mar. 2007 112 chapter 9 dc and ac operating conditions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.10 100m / mii media independent interface: transmit latency table 9-17 lists the significant time periods for the mii / 100 stream interf ace transmit latency. the time periods consist of timings of signals on the following pins: ? txen ? txclk ? txd (that is, txd[3:0]) ? tp_tx (that is, tp_txp and tp_txn) figure 9-11 shows the timing diagram for the time periods. ? the ieee maximum is 18 bit times. figure 9-11. mii / 100m stream inte rface transmit latency timing diagram table 9-17. mii / 100m stream interface transmit latency time period parameter conditions min. typ. max. units t1 txen sampled to mdi output of first bit of /j/ ? mii mode ? 2.8 3 bit times txen txclk txd tp_tx ? ? shown unscrambled. t1 preamble /k/ preamble /j/
chapter 9 dc and ac operating conditions ics1893cf, rev. f, 03/01/07 mar. 2007 113 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.11 100m mii: carrier assertion/de-assertion (half-duplex transmission) table 9-18 lists the significant time periods for the 100m mii carrier assertion/de-assertion during half-duplex transmission. the time periods consis t of timings of signals on the following pins: ? txen ? txclk ? crs figure 9-12 shows the timing diagram for the time periods. figure 9-12. 100m mii carrier asser tion/de-assertion timing diagram (half-duplex transmission only) table 9-18. 100m mii carrier assertion/de-assertion (half-duplex transmission only) time period parameter condi- tions min. typ. max. units t1 txen sampled asserted to crs assert 0 3 4 bit times t2 txen de-asserted to crs de-asserted 0 3 4 bit times t2 t1 txen txclk crs
ics1893cf, rev. f, 03/01/07 mar. 2007 114 chapter 9 dc and ac operating conditions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.12 10m mii: carrier assertion/de-assertion (half-duplex transmission) table 9-19 lists the significant time periods for the 10m mi i carrier assertion/de-assertion during half-duplex transmission. the time periods consist of timings of signals on the following pins: ? txen ? txclk ? crs figure 9-13 shows the timing diagram for the time periods. figure 9-13. 10m mii carrier assertion/de-assertion timing diagram (half-duplex transmission only) table 9-19. 10m mii carrier assertion/de-asserti on (half-duplex transmission only) time period parameter condi- tions min. typ. max. units t1 txen asserted to cr s assert 0 ? 2 bit times t2 txen de-asserted to crs de-asserted 0 2 4 bit times t2 t1 txen txclk crs
chapter 9 dc and ac operating conditions ics1893cf, rev. f, 03/01/07 mar. 2007 115 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.13 100m mii media independent interface: receive latency table 9-20 lists the significant time periods for the 100m mii / 100m stream interface receive latency. the time periods consist of timings of signals on the following pins: ? tp_rx (that is, tp_rxp and tp_rxn) ? rxclk ? rxd (that is, rxd[3:0]) figure 9-14 shows the timing diagram for the time periods. figure 9-14. 100m mii / 100m stream interface: receive latency timing diagram table 9-20. 100m mii / 100m stream interface receive latency timing time period parameter conditions min. typ. max. units t1 first bit of /j/ into tp_rx to /j/ on rxd 100m mii ? 16 17 bit times rxclk tp_rx ? ? shown unscrambled. rxd t1
ics1893cf, rev. f, 03/01/07 mar. 2007 116 chapter 9 dc and ac operating conditions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.14 100m media independent interface: i nput-to-carrier assertion/de-assertion table 9-21 lists the significant time periods for the 100m mdi input-to-carrier assertion/de-assertion. the time periods consist of timings of signals on the following pins: ? tp_rx (that is, tp_rxp and tp_rxn) ? crs ? col figure 9-15 shows the timing diagram for the time periods. ? the ieee maximum is 20 bit times. ? the ieee minimum is 13 bit times, and the maximum is 24 bit times. figure 9-15. 100m mdi input to carrier assertion / de-assertion timing diagram table 9-21. 100m mdi input-to-carrier assertion/de-assertion timing time period parameter conditions min. typ. max. units t1 first bit of /j/ into tp_rx to crs assert ? ? 10 ? 14 bit times t2 first bit of /j/ into tp_rx while transmitting data to col assert ? half-duplex mode 9 ? 13 bit times t3 first bit of /t/ into tp_rx to crs de-assert ? ?13?18bit times t4 first bit of /t/ received into tp_rx to col de-assert ? half-duplex mode 13 ? 18 bit times t1 t2 t3 t4 first bit first bit of /t/ ? shown unscrambled. tp_rx ? crs col
chapter 9 dc and ac operating conditions ics1893cf, rev. f, 03/01/07 mar. 2007 117 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.15 reset: power-on reset table 9-22 lists the significant time periods for the power-on reset. the time periods consist of timings of signals on the following pins: ? vdd ? txclk figure 9-16 shows the timing diagram for the time periods. figure 9-16. power-on reset timing diagram table 9-22. power-on reset timing time period parameter conditions min. typ. max. units t1 vdd 2.7 v to reset complete ? 40 45 500 ms txclk valid vdd 2.7 v t1
ics1893cf, rev. f, 03/01/07 mar. 2007 118 chapter 9 dc and ac operating conditions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.16 reset: hardware reset and power-down table 9-23 lists the significant time periods for the hardw are reset and power-down reset. the time periods consist of timings of signals on the following pins: ? ref_in ? resetn ? txclk figure 9-17 shows the timing diagram for the time periods. figure 9-17. hardware reset a nd power-down timing diagram table 9-23. hardware reset and power-down timing time period parameter condi- tions min. typ. max. units t1 resetn active to device isol ation and initialization ? ? 60 ? ns t2 minimum resetn pulse width ? 500 40 ? ns t3 resetn released to txclk valid ? ? 35 500 ms ref_in resetn t1 t2 t3 txclk valid power consumption (ac only)
chapter 9 dc and ac operating conditions ics1893cf, rev. f, 03/01/07 mar. 2007 119 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.17 10base-t: heartbeat timing (sqe) table 9-24 lists the significant time periods for the 10base-t heartbeat (tha t is, the signal quality error). the time periods consist of timings of signals on the following pins: ? txen ? txclk ? col figure 9-18 shows the timing diagram for the time periods. note: 1. for more information on 10base-t sqe operations, see section 6.5.10, ?10base-t operation: sqe test? . 2. in 10base-t mode, one bit time = 100 ns. figure 9-18. 10base-t heartbeat (sqe) timing diagram table 9-24. 10base-t heartbeat (sqe) timing time period parameter conditions min. typ. max. units t1 col heartbeat asse rtion delay from txen de-assertion 10base-t half duplex ? 850 1500 ns t2 col heartbeat assertion duration 10base-t half duplex ? 1000 1500 ns t2 t1 txen txclk col
ics1893cf, rev. f, 03/01/07 mar. 2007 120 chapter 9 dc and ac operating conditions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.18 10base-t: jabber timing table 9-25 lists the significant time periods for the 10base- t jabber. the time periods consist of timings of signals on the following pins: ? txen ? tp_tx (that is, tp_txp and tp_txn) ? col figure 9-19 shows the timing diagram for the time periods. note: for more information on 10base-t jabber operations, see section 6.5.9, ?10base-t operation: jabber? . figure 9-19. 10base-t jabber timing diagram table 9-25. 10base-t jabber timing time period parameter conditions min. typ. max. units t1 jabber activation time 10base-t half duplex 20 ? 35 ms t2 jabber de-activation time 10base-t half duplex 300 ? 325 ms txen tp_tx col t1 t2
chapter 9 dc and ac operating conditions ics1893cf, rev. f, 03/01/07 mar. 2007 121 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.19 10base-t: normal link pulse timing table 9-26 lists the significant time periods for the 10base-t normal link pulse (which consists of timings of signals on the tp_txp pins). figure 9-20 shows the timing diagram for the time periods. figure 9-20. 10base-t normal link pulse timing diagram table 9-26. 10base-t normal link pulse timing time period parameter conditions min. typ. max. units t1 normal link pulse width 10base-t ? 100 ? ns t2 normal link pulse to normal link pulse period 10base-t 8 20 25 ms t1 t2 tp_txp
ics1893cf, rev. f, 03/01/07 mar. 2007 122 chapter 9 dc and ac operating conditions ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. 9.5.20 auto-negotiation fast link pulse timing table 9-27 lists the significant time periods for the ics189 3cf auto-negotiation fast link pulse. the time periods consist of timings of signals on the following pins: ? tp_txp ? tp_txn figure 9-21 shows the timing diagram for one pair of thes e differential signals, for example tp_txp minus tp_txn. figure 9-21. auto-negotiation fast link pulse timing diagram table 9-27. auto-negotiation fast link pulse timing time period parameter conditions min. typ. max. units t1 clock/data pulse width ? ? 90 ? ns t2 clock pulse-to-data pulse timing ? 55 60 70 s t3 clock pulse-to-clock pulse timing ? 110 125 140 s t4 fast link pulse burst width ? ? 5 ? ms t5 fast link pulse burst to fast link pulse burst ? 10 15 25 ms t6 number of clock/data pulses in a burst ? 15 20 30 pulses clock pulse clock pulse data pulse t1 t3 t2 t4 t5 t1 flp burst flp burst differential twisted pair transmit signal differential twisted pair transmit signal
chapter 10 physical dimensions of ics1893cf ics1893cf, rev. f, 03/01/07 mar. 2007 123 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. chapter 10 physical dimensions of ics1893cf package figure 10-1. ics1893cf 300 mil ssop physical dimensions
ics1893cf, rev. f, 03/01/07 mar. 2007 124 chapter 10 physical dimensions of ics1893cf ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. figure 10-2. ics1893ck thermally enhanced, very thin, fine pitch, quad flat / no lead plastic package
chapter 11 ordering information ics1893cf, rev. f, 03/01/07 mar. 2007 125 ics1893cf data sheet rev. f - release copyright ? 2007, integrated device technology, inc. all rights reserved. chapter 11 ordering information figure 11-1. shows ordering information for the ics1893cf. part / order number ma rking package temperature ics1893cf 1893cf 48-lead 300-mil ssop 0 c to 70 c ics1893cflf 1893cflf 48-lead ssop lead/pb-free 0 c to 70 c ics1893cft 1893cf 48-lead 300-mil ssop, tape and reel 0 c to 70 c ics1893cflft 1893cflf 48-lead ssop lead/pb-free, tape and reel 0 c to 70 c ics1893cfi 1893cfi 48-lead 300-mil ssop -40 c to 85 c ics1893cfilf 1893cfilf 48-lead ssop lead/pb-free -40 c to 85 c ICS1893CFIT 1893cfi 48-lead 300-mil ssop, tape and reel -40 c to 85 c ics1893cfilft 1893cfilf 48-lead ssop lead/pb-free, tape and reel -40 c to 85 c ics1893ck 1893ck 56-lead 8x8 mlf2 0 c to 70 c ics1893cklf 1893cklf 56-lead mlf2 lead/pb-free 0 c to 70 c ics1893ckt 1893ck 56-lead 8x8 mlf2, tape and reel 0 c to 70 c ics1893cklft 1893cklf 56-lead mlf2 lead/pb-free, tape and reel 0 c to 70 c ics1893cki 1893cki 56-lead 8x8 mlf2 -40 c to 85 c ics1893ckilf 1893ckilf 56-lead mlf2 lead/pb-free -40 c to 85 c ics1893ckit 1893cki 56-lead 8x8 mlf2, tape and reel -40 c to 85 c ics1893ckilft 1893ckilf 56-lead mlf2 lead/pb-free, tape and reel -40 c to 85 c
ics1893cf, rev. f, 03/01/07 mar. 2007 126 chapter 11 ordering information ics1893cf data sheet - release copyright ? 2007, integrated device technology, inc. all rights reserved. corporate headquarters integrated device technology, inc. www.idt.com for sales 800-345-7015 408-284-8200 fax: 408-284-2775 for tech support 408-284-4522 clockhelp@idt.com innovate with idt and accelerate your future networks. contact: www.idt.com

▲Up To Search▲

Price & Availability of ICS1893CFIT

	To Download ICS1893CFIT Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .